Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Get a second opinion from GPT, Gemini, and Grok in Claude Code, Codex, Cursor, Kiro, Antigravity, OpenCode, or any other MCP host - plus local models (Ollama, LM Studio) and 400+ more models through OpenRouter, including Qwen, Kimi, and DeepSeek. Seven domain experts (Architect, Code Reviewer, Security Analyst, and four more) review your plans, find bugs, and debate edge cases until they agree.
Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro, OpenCode. Measures the models' usefulness, too.
When three models argue, the real bug reveals itself. Round 1 = independent top findings. Round 2 = each model dunks on the others' picks. The disagreement matrix shows where they diverge; the conclusion shows what to actually fix first.
The dashboard (/deliberation:dashboard, opt-in with "dashboard": { "enabled": true }) is a read-only page on 127.0.0.1. Live follows runs as they happen, Runs keeps the history (with the repo and workspace each run came from, grouped by git remote org/repo, and a project filter that picks a whole repo or one workspace), Config shows the effective config, Stats shows usage and provider health, and Analyzer shows which models agree more than they add (drop candidates), which projects fail or run slow, and whether request size predicts latency and timeouts, with a suggested timeout. For a run you get:
The CAPTURE and PII badges show what was recorded. The default capture is metadata only, and PII is redacted unless dashboard.showPII is on.
Your coding agent can ask GPT, Gemini, Grok, local models (Ollama, LM Studio), or any OpenAI-compatible model (via OpenRouter) for help through MCP. Deliberation handles the wiring for each provider so you just write the prompt. Each expert has a distinct specialty and can advise or implement.
It is not tied to Claude Code. The same MCP server runs on any MCP host, and Codex, Cursor, Kiro, Antigravity, and OpenCode also get native plugins with the experts and delegation guidance built in (see Install). Claude Code gets the most complete version: slash commands and auto-routing rules on top of the same server.
You can use any subset of the providers. Deliberation detects which are configured and routes
accordingly. OpenRouter is advisory-only and config-driven: models are declared in
~/.config/deliberation/config.json (Windows: %APPDATA%\deliberation\config.json; override
with DELIBERATION_CONFIG) and hot-reload without restarting your host.
Pick the path for your host:
1. Add the marketplace - antonbabenko/agent-plugins
Recent blog post: /plugin marketplace add antonbabenko/agent-plugins
2. Install the plugin
/plugin install deliberation@antonbabenko
3. Run setup
/deliberation:setup
Claude now routes complex tasks to your GPT, Gemini, Grok, local (Ollama, LM Studio), and OpenRouter experts (every provider advises; only Gemini can also implement).
Setup is a one-time step. The MCP servers are registered by the plugin manifest, so they load automatically and stay current across updates.
/plugin marketplace update antonbabenko # pull the new version from the marketplace
/deliberation:reload-mcp # audit processes & recycle dashboard daemon
/reload-plugins # reconnect the MCP servers (or restart Claude Code)
Updating on non-Claude hosts: hosts that run the standalone server via npx -y @antonbabenko/deliberation-mcp get the latest published version on each fresh resolve. npx
caches resolved packages, so if a host serves an old build, clear the npx cache
(rm -rf ~/.npm/_npx) or pin/refresh the version. Run bash scripts/commands/reload-mcp.sh
(or trigger the reload-mcp skill / command on Codex, Antigravity, OpenCode) to audit
running worker processes and recycle the background dashboard daemon safely.
deliberation MCP server (standalone, works with any agents)The orchestration server is also published on its own - npm @antonbabenko/deliberation-mcp, Official MCP Registry name io.github.antonbabenko/deliberation.
One-click install:
Add this to your host's MCP config (most hosts use the mcpServers key):
{
"mcpServers": {
"deliberation": {
"command": "npx",
"args": ["-y", "@antonbabenko/deliberation-mcp"],
"env": {
"XAI_API_KEY": "xai-...",
"OPENROUTER_API_KEY": "sk-or-v1-..."
}
}
}
}
The env block is how you set provider keys outside Claude Code. GPT and Gemini do not read keys here - they use the codex and agy CLIs (logged in separately), so drop those lines if you only use GPT/Gemini. XAI_API_KEY enables Grok; OPENROUTER_API_KEY enables OpenRouter (which also needs models declared in ~/.config/deliberation/config.json - the canonical XDG path, Windows %APPDATA%\deliberation\config.json - or point elsewhere with DELIBERATION_CONFIG). The one-click buttons above cannot carry secrets - add the env block by hand after installing.
Per-host config location and the key it expects:
Provider prerequisites are the same as the plugin (see Requirements): the Codex CLI for GPT, agy for Gemini, XAI_API_KEY for Grok, and OPENROUTER_API_KEY plus ~/.config/deliberation/config.json for OpenRouter (Windows: %APPDATA%\deliberation\config.json; override the config path with DELIBERATION_CONFIG).
Tools exposed: ask-all, consensus (the full convergence loop in one call, or a single synthesis pass with synthesizeAlways:true), consensus-step (drive the loop yourself, one action per call), ask-gpt / ask-gemini / ask-grok / ask-openrouter, panel + ask-one (discover the active provider set, then call providers individually - issue them in parallel for visible per-provider progress), analyze (read-only run analytics over the debug log + sessions: per-model latency / tokens + verdict agreement, with advisory tuning suggestions; configuredOnly and since keep the report to models you still run and a period you choose), the seven experts (architect, plan-reviewer, scope-analyst, code-reviewer, security-analyst, researcher, debugger), and the session tools (session-get / session-revisit / session-annotate). Every result carries ms + the effective reasoningEffort (HTTP providers add token usage). An optional debug log ("debug": { "enabled": true }) records latency / tokens / votes - never prompts or responses. An optional local dashboard ("dashboard": { "enabled": true }, then deliberation-mcp dashboard) draws every run as a live state graph in your browser; panel returns a runId that ask-one accepts, so a parallel fan-out shows as one run. These are server-side, so they work on every MCP host, not just Claude Code (see the tool guide).
The package also ships a deliberation-setup bin. Run it once with npx -y --package @antonbabenko/deliberation-mcp deliberation-setup to write a starter ~/.config/deliberation/config.json (it never overwrites an existing one). The plain npx -y @antonbabenko/deliberation-mcp form runs the default bin (the server), which is what your MCP host launches. For host rule wiring, see the tool guide and the per-host snippets in examples/.
The repo ships a Dockerfile for running the standalone server in a container. It wraps the stdio server in mcp-proxy, the same shape MCP hosting providers expect:
docker build -t deliberation-mcp .
docker run -i --rm \
-e XAI_API_KEY -e OPENROUTER_API_KEY \
-v ~/.config/deliberation:/home/node/.config/deliberation:ro \
deliberation-mcp
Grok and OpenRouter work from the keys alone. GPT and Gemini do not - they shell out to the codex and agy CLIs, which are not in the image, so those two providers report not-found / missing-cli inside the container.
Beyond the raw MCP config above, deliberation ships native plugin artifacts for five hosts so the experience matches the Claude Code plugin (persona-bearing experts + when-to-delegate guidance, not just bare tools). All of these are generated from the canonical sources by node scripts/sync-hosts.js and committed, so they never drift (a CI drift test enforces it). Each host scans the repo for its own files:
Provider credentials work the same as the standalone server (GPT via the Codex CLI, Gemini via agy, XAI_API_KEY for Grok, OPENROUTER_API_KEY for OpenRouter) - set only the providers you use. The MCP server already injects each expert persona server-side, so these native files add the host's command/steering surface, not duplicated logic.
Full per-host install guides: docs/hosts/ - Antigravity & Gemini, Cursor, Codex CLI, Kiro, OpenCode.
You need at least one provider:
npm install -g @openai/codex, then codex login (ChatGPT subscription; codex login --device-auth on a remote machine, one login per machine). A ChatGPT Business/Enterprise workspace can set CODEX_ACCESS_TOKEN instead. With neither, codex uses CODEX_API_KEY; OPENAI_API_KEY is never used.agy and login.XAI_API_KEY (get a key at https://console.x.ai).OPENROUTER_API_KEY (get a key at https://openrouter.ai/keys), then declare models in ~/.config/deliberation/config.json (Windows: %APPDATA%\deliberation\config.json; override with DELIBERATION_CONFIG). Works with any OpenAI-compatible endpoint (Ollama, vLLM, LM Studio, HuggingFace Inference) - auth is skipped automatically when the key env var is empty. Supports custom OpenRouter presets (e.g. cheapest-first) to optimize inference cost and provider routing.Windows note (CLI providers). npm install -g on Windows installs a codex.cmd shim, not an
executable, and Node cannot launch a .cmd directly - so GPT calls used to fail with nothing but a
spawn error. deliberation now resolves the CLI itself (PATHEXT, falling back to the package's own
entry point) and keeps it out of a shell. If resolution ever misses on your machine, point
CODEX_BIN (GPT) or AGY_BIN (Gemini) at the real executable. Grok and OpenRouter are unaffected -
they are HTTP bridges and spawn nothing.
Claude Code on the web note. The web host caps every MCP tool call at 60s
(MCP_TOOL_TIMEOUT=60000). The plugin manifest overrides that per server: each deliberation
server declares "timeout": 1800000 (30 min, which Claude Code applies ahead of
MCP_TOOL_TIMEOUT) and mirrors it into the server's env so the plugin's own clamp tracks
the real cap. Nothing to set in the environment. A timeout result whose message still names
MCP_TOOL_TIMEOUT=60000 means an older plugin install: claude plugin update deliberation@antonbabenko and start a new session. /deliberation:doctor reports the cap,
the codex credential, and a missing agy; the panel skips providers that cannot answer
(panel.unavailable) instead of waiting on them. For GPT, do not copy your laptop's
~/.codex/auth.json into the container: a ChatGPT login's refresh token works once, so both
the other copy stops working as soon as one of them refreshes. On Plus/Pro, the first GPT call
in a session starts codex login --device-auth and shows its link and code (a dialog when the
host supports it, else in the result); approve it and GPT answers. On Business/Enterprise, set
CODEX_ACCESS_TOKEN. See SETUP.md.
Bundled with the Claude Code plugin (available once installed; OpenCode gets the ask-*, consensus, and analyze commands, and every other host calls the matching MCP tools directly):
/setup can also install short aliases (/ask-gpt, /ask-gemini, /ask-grok, /ask-openrouter, /ask-all, /consensus) into ~/.claude/commands/. This is opt-in. Existing same-named commands are kept by default; setup asks before overwriting any of them. /deliberation:uninstall removes an alias only if it is byte-identical to the bundled copy.
analyze is deliberately excluded: /analyze is a common name and a bare copy collides with any other plugin that ships one. Use /deliberation:analyze, which is always available. If an earlier setup installed ~/.claude/commands/analyze.md, setup now points out the path so you can delete it. /deliberation:uninstall also lists analyze, but its byte-identical guard only matches a copy of the current bundled file - an alias copied from an older release will differ and is deliberately left alone rather than deleted on a guess.
Describe your task. Your agent detects when an expert helps and delegates automatically (the examples show Claude Code):
You: "Is this authentication flow secure?"
Claude: routes to the Security Analyst, then synthesizes the findings.
You can also ask explicitly: "Ask GPT to review this architecture", "Ask Gemini to...", or "Ask Grok to...". Each expert runs read-only for analysis; Gemini can also run with write access to apply fixes, and your agent picks the mode from your request.
Or invoke the slash commands directly - see Commands above.
This section uses the Claude Code command names, and "Claude" means the host agent that orchestrates the run. On other hosts your own agent plays that role through the consensus-step tool (or the server plays it with consensus), under the same rules.
/ask-gpt, /ask-gemini, /ask-grok, and /ask-all are the quick commands: each dispatches one or three external models, Claude reads the output, and you get one synthesized answer. Single shot, no loop, no peer round.
/consensus is the heavy one. Same parallel dispatch, but with a peer-review round and a multi-round loop that stops only when the models agree. The cost: the orchestrator (Claude) writes the review prompt, casts a vote, decides which objections are real, and runs the loop. Left alone, that setup can quietly rubber-stamp its own plan. Four guards stop that.
The four guards:
missing-auth, for example) drops out of the count instead of jamming the loop.The /ask-* commands carry a lighter version of the same rule. The external model only advises: Claude reads the output, applies its own judgment, and owns the synthesized answer. When the models agree, that is input, not a verdict.
Every delegate prompt also carries today's UTC date and a rule against calling an unrecognized model, tool, or version non-existent from memory: a model trained months ago marks such a claim [unverified] instead of filing it as a critical issue. Looking up the actual facts stays with Claude, which has tools; Grok and OpenRouter have none. See TECHNICAL.md.
/consensus is a thin driver over the core convergence engine (core/consensus-loop.js); the loop mechanics - round counting, the convergence rule, the configurable max-rounds cap, history, and the confidence label - live in the engine, not the command. Each round:
The loop converges when at least one responding external approves, none reject, zero critical issues remain accepted, and Claude adjudicates APPROVE - so Claude cannot self-approve. It otherwise stops at consensus.maxRounds (default 5, configurable) as unresolved. The confidence label reflects how fast it settled (round 1 = high, 2-3 = medium, 4-5 = low).
A round only pays for voices that can still answer: a peer that fails 2 rounds running is dropped from the panel (reported once as droppedProviders, then never dispatched again), and the whole loop stops at consensus.maxWallMs (default 30 min) rather than starting another round. Both apply on every driver. See TECHNICAL.md.
The same engine backs the entry points other hosts use: the consensus tool (runs the whole loop server-side in one call with a provider arbiter, or a single synthesis pass with synthesizeAlways:true) and consensus-step (drive it yourself, one action per call). See TECHNICAL.md for the taxonomy and the engine contract.
An earlier revision ran an extra "Stage 2" anonymized peer cross-review (each model scoring the others' answers blind, adapted from karpathy/llm-council). The engine-driven rewrite removed it to keep one source of truth; it may return as an engine feature.
Full setup and configuration reference lives in SETUP.md. It covers:
read-only) vs implementation (workspace-write), chosen automatically from your request~/.config/deliberation/config.json), the DELIBERATION_CONFIG override, and hot-reloadproviders, models, routing, consensus, sessions, debug, orientation, dashboard - with a minimal exampleaskAll / consensus eligibility, fan-out, reasoningEffort, and arbiter selection; consensus also configures the round cap (maxRounds) and wall-time budget (maxWallMs, default 30 min)providers.codex.model and providers.codex.reasoningEffort pin what codex exec runs, winning over ~/.codex/config.tomlproviders.defaults.timeout raises the per-call ceiling for every provider at once; providers.<name>.timeout overrides one, and a pinned model's models.<id>.timeout still wins. A host cap (MCP_TOOL_TIMEOUT, set by Claude Code on the web) clamps all of them and is named in the timeout message. A rate-limited (HTTP 429) call is retried once, honoring the upstream's Retry-After/consensus loop) and the session-* tools; sessions.captureText (default off) additionally stores provider response bodies (scrubbed)dashboard.capture picks metadata only (default) or full prompts and responses; secrets are scrubbed on write and PII is redacted on serve unless dashboard.showPII is on. Loopback only, token-protected. Every run records its project (grouped by git remote org/repo, with the checkout it was called from as the workspace), every provider call its request size and the timeout it actually got, which the Analyzer tab turns into drop candidates and timeout advice. Start it with /deliberation:dashboard or deliberation-mcp dashboard; restart it with /deliberation:dashboard restart or npm run dashboard:restart, stop it with deliberation-mcp dashboard --stopConfig history records sanitized effective snapshots and run provenance when
telemetry is enabled. Dashboard Stats shares analyze time/config filters; Config
shows separate Ask/Consensus effort and observed runtime active/pending settings.
Parallel peers share the longest selected timeout within host/consensus budgets
(routing.timeoutPolicy: "per-provider" opts out). Pass the panel fanoutId to
every progressive ask-one to pin settings and share a deadline, even without
dashboard logging. Use analyze {groupBy:"config", since:"24h"} for historical
cohorts, optionally narrowed by full configId or activationId.
For provider internals, environment variables, and manual MCP setup, see TECHNICAL.md.
Contributions welcome. See CONTRIBUTING.md for the workflow, commit conventions, and the automated release process.
Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro, OpenCode. Measures th
ภาพรวม
Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro, OpenCode. Measures the models' usefulness, too.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Deliberation ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-11 Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro, OpenCode. Measures the models' usefulness, too.
