Structured step-by-step reasoning for complex problem solving.
Zen MCP
Multi-model orchestration — let Claude consult Gemini, GPT, and o-series as sub-agents.
Quick answer
What it does
Provides workflow tools that route to a chosen model, plus higher-level workflows (consensus across multiple models, deep thinking, codereview) that orchestrate multiple model calls inside one MCP tool.
Best for
- Multi-model consensus
- Deep debugging
- Architecture decisions
- Cross-model code review
Not for
- Latency-sensitive work
- Routine single-step tasks
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "zen-mcp": { "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export GEMINI_API_KEY=OPTIONAL # export OPENAI_API_KEY=OPTIONAL # export OPENROUTER_API_KEY=OPTIONAL claude mcp add zen-mcp -- uvx zen-mcp-serverRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "zen-mcp": { "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "zen-mcp": { "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "zen-mcp": { "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "zen-mcp": { "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "uvx", "args": [ "zen-mcp-server" ], "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.zen-mcp] command = "uvx" args = [ "zen-mcp-server", ] env = { GEMINI_API_KEY = "${GEMINI_API_KEY}", OPENAI_API_KEY = "${OPENAI_API_KEY}", OPENROUTER_API_KEY = "${OPENROUTER_API_KEY}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "zen-mcp": { "command": { "path": "uvx", "args": [ "zen-mcp-server" ] }, "env": { "GEMINI_API_KEY": "${GEMINI_API_KEY}", "OPENAI_API_KEY": "${OPENAI_API_KEY}", "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneZen MCP doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
GEMINI_API_KEY,OPENAI_API_KEY,OPENROUTER_API_KEYin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Security & scope
- Access scope
- Network
- Sandbox
- Calls outbound to whichever LLM providers you configure. Prompts and outputs flow through those providers under their privacy policies.
- Gotchas
- Multi-model calls amplify token spend — set per-provider budgets.
- Provider-specific features (Anthropic prompt caching) do not pass through universally.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. agent orchestration work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-agent-orchestration
Compare Zen MCP MCP vs [Sequential Thinking MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/zen-mcp - top-mcps.com listing for Sequential Thinking
Install the Zen MCP MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/zen-mcp (fetch https://top-mcps.com/mcp/zen-mcp.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (GEMINI_API_KEY, OPENAI_API_KEY, OPENROUTER_API_KEY) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Agent Orchestration MCPs
Other tools in the same category worth evaluating.
Persistent knowledge graph memory across AI conversations.
AI-driven task management and decomposition for long-running agent projects.
Compared with Zen MCP
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Agent Orchestration? See all Agent Orchestration MCPs →