Anthropic Billing vs Context Doctor
A side-by-side look at the Anthropic Billing and Context Doctor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Anthropic Billing for conversational ai work over a hosted endpoint; choose Context Doctor 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 Anthropic Billing when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
anthropic_billing_list_accounts, anthropic_billing_usage, anthropic_billing_cost.
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 | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 39/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | 4 |
| Full listing | View Anthropic Billing | View Context Doctor |
Tools & capabilities
Anthropic Billing tools 9
anthropic_billing_list_accountsList Anthropic Billing admin API connections linked to this install.anthropic_billing_usageGet normalized Anthropic Messages API usage for a date range. The adapter drains report pagination internally.anthropic_billing_costGet normalized Anthropic cost report for a date range. Returns compact totals and daily costs.show_versionShow the current MCP platform and adapter versions.report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
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
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.
Anthropic Billing
{
"mcpServers": {
"anthropic-billing": {
"url": "https://api.mcp.ai/p_anthropic_billing"
}
}
}
Context Doctor
{
"mcpServers": {
"context-doctor": {
"command": "npx",
"args": [
"-y",
"context-doctor"
]
}
}
}
Frequently asked questions
Anthropic Billing is categorized under Conversational AI and uses a remote HTTP/SSE transport. Context Doctor belongs to Conversational AI and uses a local stdio subprocess. Pick Anthropic Billing for conversational ai work and Context Doctor 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.
Anthropic Billing has no declared pricing — check the project's own site. Context 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 anthropic-billing and context-doctor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Anthropic Billing has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Context Doctor has 56/100 (Good) with 1 views, 0 installs and 2 GitHub stars.