CompletionKit vs MCP Doctor
A side-by-side look at the CompletionKit and MCP Doctor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CompletionKit for conversational ai work over a hosted endpoint; choose MCP Doctor 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 CompletionKit when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
COMPLETION_KIT_ENCRYPTION_PRIMARY_KEY, COMPLETION_KIT_ENCRYPTION_DETERMINISTIC_KEY, COMPLETION_KIT_ENCRYPTION_KEY_DERIVATION_SALT, OPENAI_API_KEY, ANTHROPIC_API_KEY, OLLAMA_API_ENDPOINT, OPENROUTER_API_KEY.
Choose MCP Doctor when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENAI_API_KEY, OPENAI_BASE_URL, MCP_DOCTOR_MODEL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Developer Tools |
| Quality signal | 41/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | COMPLETION_KIT_ENCRYPTION_PRIMARY_KEYCOMPLETION_KIT_ENCRYPTION_DETERMINISTIC_KEYCOMPLETION_KIT_ENCRYPTION_KEY_DERIVATION_SALTOPENAI_API_KEYANTHROPIC_API_KEYOLLAMA_API_ENDPOINTOPENROUTER_API_KEY | OPENAI_API_KEYOPENAI_BASE_URLMCP_DOCTOR_MODEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CompletionKit | View MCP Doctor |
Tools & capabilities
CompletionKit tools
No tool names declared yet. Check the project README from the listing page.
MCP Doctor 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.
CompletionKit
{
"mcpServers": {
"completionkit": {
"url": "https://your-app.com/completion_kit/mcp"
}
}
}
MCP Doctor
{
"mcpServers": {
"mcp-doctor": {
"command": "uvx",
"args": [
"mcp-doctor"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"OPENAI_BASE_URL": "YOUR_OPENAI_BASE_URL_HERE",
"MCP_DOCTOR_MODEL": "YOUR_MCP_DOCTOR_MODEL_HERE"
}
}
}
}
Frequently asked questions
CompletionKit is categorized under Conversational AI and uses a remote HTTP/SSE transport. MCP Doctor belongs to Developer Tools and uses a local stdio subprocess. Pick CompletionKit for conversational ai work and MCP Doctor 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.
CompletionKit has no declared pricing — check the project's own site. MCP Doctor 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 completionkit and mcp-doctor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CompletionKit has a quality signal of 41/100 (Fair) with 3 views, 0 installs and 3 GitHub stars. MCP Doctor has 37/100 (Fair) with 4 views, 0 installs and 1 GitHub stars.