Chatpack MCP vs Docs
A side-by-side look at the Chatpack MCP and Docs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chatpack MCP for developer tools work as a local process; choose Docs for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 224 | 1,433 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Chatpack MCP | View Docs |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
Docs tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Docs
No confirmed install command for Docs yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. Docs belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Chatpack MCP for developer tools work and Docs for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Docs has no confirmed install command yet — follow its own setup instructions.
Chatpack MCP is listed as free. Auth: no auth required. Docs has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chatpack-mcp and docs-6 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 3 views, 0 installs and 224 GitHub stars. Docs has 41/100 (Fair) with 2 views, 0 installs and 1,433 GitHub stars.