Docs vs MCP Server
A side-by-side look at the Docs and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Docs for developer tools work; choose MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server 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, search_model.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 41/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,433 | 117 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Docs | View MCP Server |
Tools & capabilities
Docs tools
No tool names declared yet. Check the project README from the listing page.
MCP Server tools 2
search_docsThis tool uses vector embeddings to locally search through preprocessed CAP documentation, stored as embeddings. The process works as follows:search_modelThis tool performs fuzzy searches against names of definitions from the compiled CDS model (Core Schema Notation).
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.
Docs
No confirmed install command for Docs yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Server
{
"mcpServers": {
"mcp-server-107": {
"command": "npx",
"args": [
"-y",
"@cap-js/mcp-server"
]
}
}
}