Context Doctor vs MCP Cost Optimizer
A side-by-side look at the Context Doctor and MCP Cost Optimizer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Context Doctor for conversational ai work as a local process; choose MCP Cost Optimizer for conversational ai as a local process. 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.
Choose MCP Cost Optimizer when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
CONTROL_PLANE_URL. - You want tools like
estimate_llm_cost, analyze_llm_usage, compare_llm_models.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 56/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | CONTROL_PLANE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 3 |
| Full listing | View Context Doctor | View MCP Cost Optimizer |
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
MCP Cost Optimizer tools 3
estimate_llm_costSingle-request estimateanalyze_llm_usageCosts by model, unpriced models, duplicate opportunitycompare_llm_modelsIndependent migration scenario
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"
]
}
}
}
MCP Cost Optimizer
{
"mcpServers": {
"mcp-cost-optimizer": {
"command": "npx",
"args": [
"-y",
"mcp-cost-optimizer"
],
"env": {
"CONTROL_PLANE_URL": "YOUR_CONTROL_PLANE_URL_HERE"
}
}
}
}
Frequently asked questions
Context Doctor is categorized under Conversational AI and uses a local stdio subprocess. MCP Cost Optimizer belongs to Conversational AI and uses a local stdio subprocess. Pick Context Doctor for conversational ai work and MCP Cost Optimizer 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.
Context Doctor has no declared pricing — check the project's own site. MCP Cost Optimizer 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 context-doctor and mcp-cost-optimizer 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 0 views, 0 installs and 2 GitHub stars. MCP Cost Optimizer has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.