Codewiki MCP vs Docweave MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Codewiki MCP vs Docweave MCP
In-depth architectural comparison of the Codewiki MCP and Docweave 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.
At a Glance & Executive Verdict
Codewiki MCP
Developer Tools · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Docweave MCP
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Codewiki MCP if you need specialized Developer Tools tools running via a local process. Choose Docweave MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
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).
MCP server for codewiki.google. Search repos, fetch AI-generated wiki docs, and ask questions about any open-source repository.
Generate and read PDFs for AI agents: a generatepdf tool (HTML, a URL, or a template + JSON → PDF) and a readpdf tool (a PDF → text/markdown). Run locally with npx @docweave/mcp or use the hosted streamable-HTTP endpoint. Chromium-rendered, priced per document.
Category & Scope
Tools & Capabilities Breakdown
Codewiki MCP Tools (3)
codewiki_search_repos
Search repositories indexed by codewiki.google
codewiki_fetch_repo
Fetch generated wiki content for a repository from codewiki.google
codewiki_ask_repo
Ask a natural-language question about a repository indexed in codewiki.google
Docweave MCP Tools (2)
generate_pdf
`source` (one of: raw `html`, a public `url`, or a `template` + `data`) → a PDF.
read_pdf
`source` (`url` or `base64`) → extracted `content` (markdown or text) + `pageCount`.
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).
Codewiki MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Docweave MCP belongs to Developer Tools using local stdio subprocess. Select Codewiki MCP when you need capabilities focused on developer tools and Docweave MCP when you require tools for developer tools.