Agentcast vs Context Doctor
A side-by-side look at the Agentcast 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 Agentcast for conversational ai work as a local process; 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 Agentcast when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You want tools like
extract_json, validate_response, build_retry_prompt.
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 | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 1 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 4 |
| Full listing | View Agentcast | View Context Doctor |
Tools & capabilities
Agentcast tools 3
extract_jsonPull a JSON value out of messy LLM output. Tries the whole text, then a fenced ```json``` block, then the largest balanced {...}/[...] substring. Returns the parsed value plus which strategy succeeded.validate_responseValidate a parsed JSON value against an agentcast shape spec. Spec maps field name to type: 'string', 'number', 'boolean', 'array', 'object'. Suffix with '?' for optional. Returns valid=true on success, or valid=false with a human-readable error string suitable for retry feedback.build_retry_promptGiven an attempt history, produce the retry feedback message agentcast would append to the conversation when the model returned the wrong shape. Codifies the "validation error as feedback" pattern for non-Node MCP clients.
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.
Agentcast
{
"mcpServers": {
"agentcast": {
"command": "npx",
"args": [
"-y",
"@mukundakatta/agentcast-mcp"
]
}
}
}
Context Doctor
{
"mcpServers": {
"context-doctor": {
"command": "npx",
"args": [
"-y",
"context-doctor"
]
}
}
}
Frequently asked questions
Agentcast is categorized under Conversational AI and uses a local stdio subprocess. Context Doctor belongs to Conversational AI and uses a local stdio subprocess. Pick Agentcast 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.
Agentcast 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 agentcast and context-doctor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentcast has a quality signal of 57/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Context Doctor has 56/100 (Good) with 1 views, 0 installs and 2 GitHub stars.