Context Doctor vs EDDI
A side-by-side look at the Context Doctor and EDDI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
EDDIConversational AIConfig-driven engine that turns JSON into production-grade AI agents. Multi-agent orchestration, 12+ LLM providers, MCP/A2A protocols, RAG, persistent memory, and enterprise compliance (EU AI Act, GDPR, HIPAA). Built on Quarkus.49FairAuth: not declaredVerdict: choose Context Doctor for conversational ai work as a local process; choose EDDI for conversational ai. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Context Doctor when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
profile_context, optimize_context, pack_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E EDDI | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 56/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 387 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Context Doctor | View EDDI |
Tools & capabilities
Context Doctor tools 4
profile_contextToken breakdown by category, largest messages, findings with estimated savings. Takes either `conversation` (full JSON or text) or `sketch` (turns + large/repeated blocks, for chat apps)optimize_contextRewrites the conversation: dedupe, trim stale tool results, strip base64, optional history pruningpack_contextOnly the chunks of large local files or folders (or passed `text`) that a question needs, within `max_tokens`; outline without a query; `ids` to fetch more. Reads no files over HTTPcontext_best_practicesCurated checklist, optionally specialized for Anthropic / OpenAI
EDDI 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.
Context Doctor
{
"mcpServers": {
"context-doctor": {
"command": "npx",
"args": [
"-y",
"context-doctor"
]
}
}
}
EDDI
No confirmed install command for EDDI yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Context Doctor is categorized under Conversational AI and uses a local stdio subprocess. EDDI belongs to Conversational AI and uses an install path we have not confirmed yet. Pick Context Doctor for conversational ai work and EDDI for conversational ai.
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. EDDI has no confirmed install command yet — follow its own setup instructions.
Context Doctor has no declared pricing — check the project's own site. EDDI 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 context-doctor and eddi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context Doctor has a quality signal of 56/100 (Good) with 1 views, 0 installs and 2 GitHub stars. EDDI has 49/100 (Fair) with 0 views, 0 installs and 387 GitHub stars.