In-depth architectural comparison of the Docweave MCP and Codex Pets 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
Docweave MCP
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Codex Pets
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Docweave MCP if you need specialized Developer Tools tools running via a local process. Choose Codex Pets 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 Docweave MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
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.
Companion Gallery for Codex: public read-only registry for Codex-compatible animated companion packs. Search, preview, install community pets, generate badges/embed cards, and discover the request flow via Streamable HTTP MCP.
Category & Scope
Tools & Capabilities Breakdown
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`.
Codex Pets Tools (6)
Public read-only MCP access
Approved pet search and detail lookup
Pet installation instructions
README badge and iframe embed generation
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).
Docweave MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Codex Pets belongs to Developer Tools using local stdio subprocess. Select Docweave MCP when you need capabilities focused on developer tools and Codex Pets when you require tools for developer tools.