A side-by-side look at the AI and Kordoc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI for developer tools work as a local process; choose Kordoc for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AI when
You need dedicated capabilities in the Developer Tools domain.
No tool names declared yet. Check the project README from the listing page.
Kordoc 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.
No confirmed install command for Kordoc yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
AI is categorized under Developer Tools and uses a local stdio subprocess. Kordoc belongs to Developer Tools and uses an install path we have not confirmed yet. Pick AI for developer tools work and Kordoc 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. Kordoc has no confirmed install command yet — follow its own setup instructions.
AI has no declared pricing — check the project's own site. Kordoc is listed as free. Auth: no auth required. 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 contentrain-ai and kordoc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AI has a quality signal of 53/100 (Good) with 3 views, 0 installs and 6 GitHub stars. Kordoc has 44/100 (Fair) with 1 views, 0 installs and 2,542 GitHub stars.