Folio vs Codewiki MCP

In-depth architectural comparison of the Folio and Codewiki MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

F

Choose Folio when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Searches Folio wiki content, Reads wiki pages, Edits pages.

Explore Folio Details

Choose Codewiki MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: codewiki_search_repos, codewiki_fetch_repo, codewiki_ask_repo.

Explore Codewiki MCP Details

Feature & Specification Comparison

Specification	F Folio Developer Tools	Codewiki MCP izzzzzi Developer Tools
Summary	Self-hosted Git-backed team wiki: search, read and edit pages, data tables and whiteboards.	MCP server for codewiki.google. Search repos, fetch AI-generated wiki docs, and ask questions about any open-source repository.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "folio": {
      "url": "https://wiki.example.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "izzzzzi-codewiki-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codewiki-mcp@latest"
      ]
    }
  }
}

Related MCP Server Comparisons