Context Mode vs Agent MCP
A side-by-side look at the Context Mode and Agent MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Context Mode for coding agents work as a local process; choose Agent MCP for coding agents over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Context Mode when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ctx_batch_execute, ctx_execute, ctx_execute_file.
Choose Agent MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, AGENT_MCP_HOST, AGENT_MCP_PORT, AGENT_MCP_LOG_LEVEL, AGENT_MCP_PROJECT_DIR, AGENT_MCP_MAX_AGENTS. - You want tools like
create_agent, list_agents, terminate_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 69/100 · Great | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | OPENAI_API_KEYAGENT_MCP_HOSTAGENT_MCP_PORTAGENT_MCP_LOG_LEVELAGENT_MCP_PROJECT_DIRAGENT_MCP_MAX_AGENTS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 31,923 | 1,304 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 10 | 12 |
| Full listing | View Context Mode | View Agent MCP |
Tools & capabilities
Context Mode tools 10
ctx_batch_executeRun multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches.ctx_executeRun code in 12 languages. Only stdout enters context.ctx_execute_fileProcess files in sandbox. Raw content never leaves.ctx_indexChunk markdown into FTS5 with BM25 ranking.ctx_searchQuery indexed content with multiple queries in one call.ctx_fetch_and_indexFetch URL, chunk and index. Cache reuses content within TTL (default 24h, override per-call with `ttl: <ms>`). `ttl: 0` or `force: true` to bypass. Pass `requests: [{url, source}, ...]` + `concurrency: 1-8` for parallel multi-URL.ctx_statsShow context savings, call counts, and session statistics.ctx_doctorDiagnose installation: runtimes, hooks, FTS5, versions.ctx_upgradeUpgrade to latest version from GitHub, rebuild, reconfigure hooks.ctx_purgePermanently deletes all indexed content from the knowledge base.
Agent MCP tools 12
create_agentlist_agentsterminate_agentassign_taskview_tasksupdate_task_statusask_project_ragupdate_project_contextview_project_contextsend_agent_messagebroadcast_messagerequest_assistance
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 Mode
{
"mcpServers": {
"context-mode": {
"command": "npx",
"args": [
"-y",
"context-mode"
]
}
}
}
Agent MCP
{
"mcpServers": {
"rinadelph-agent-mcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Frequently asked questions
Context Mode is categorized under Coding Agents and uses a local stdio subprocess. Agent MCP belongs to Coding Agents and uses a remote HTTP/SSE transport. Pick Context Mode for coding agents work and Agent MCP for coding agents.
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 Mode is listed as free. Auth: no auth required. Agent MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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-mode and rinadelph-agent-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context Mode has a quality signal of 69/100 (Great) with 2 views, 0 installs and 31,923 GitHub stars. Agent MCP has 60/100 (Good) with 5 views, 0 installs and 1,304 GitHub stars.