
Agent Mcp Hub
io.github.blackaxgit由 GitHub 帳號 blackaxgit 發布v0.6.2更新於 Oct 24, 2026
One MCP server bridging the Codex, Cursor, OpenCode, Claude, and Antigravity CLI agents
概覽
本機 stdio MCP 伺服器,讓助理把提示詞交給 Codex、Cursor、OpenCode、Claude 與 Antigravity 命令列編碼代理執行,或把同一提示詞平行分送給全部代理。
- 可以做什麼
- 把提示詞委派給單一命令列編碼代理(codex、cursor、opencode、claude、agy),可指定模型、工作目錄與逾時
- 把同一提示詞平行送給所有已安裝代理,並排比較結果
- 列出已安裝且在 PATH 上的代理命令列,並提供健康檢查
- 讓一個代理在 git 工作區中修改程式碼,擷取 diff 後由另一個代理審查並給出 PASS/WARN/FAIL 結論
- 對未安裝、未登入、未設定、逾時或串流中斷的代理回傳分類清楚、可據以處理的錯誤
- 適用情境
- 適合已同時使用多個命令列編碼代理的人:希望在單一 MCP 用戶端中呼叫任一個代理、比較它們的回答,或讓不同代理交叉審查程式碼變更,而不必切換工具。
- 執行需求
- 以 MCP 用戶端的子程序在本機透過 stdio 執行(npm 套件 agent-mcp-hub,可全域安裝或使用 npx)。每個被包裝的命令列工具需個別安裝並登入;hub 本身未宣告任何 API 金鑰。選用環境變數:MCP_AGENTS 允許清單、MCP_CONFIRM、MCP_AGENT_TIMEOUT_MS 與 MCP_AGENT_IDLE_TIMEOUT_MS。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Agent Mcp Hub,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
agent-mcp-hub
One MCP server that bridges multiple CLI coding agents — Codex, Cursor, OpenCode, Claude, and Antigravity — into any MCP client.
stdio only — by design. The hub ships no Docker image and no HTTP transport (both were removed during the 0.5.x line). A containerised or remote server cannot see the caller's repository path and cannot reuse the caller's CLI logins — it would break the product contract on both halves. The hub runs as a child process of your MCP client, on your machine, as you.
Tools
Agent tools accept prompt (required), model, cwd, timeoutMs (total runtime
cap, default 1800000 = 30 min), and idleTimeoutMs (inactivity cap, default 300000
= 5 min). See Long-running tasks & timeouts.
Known limitation: opencode prompts may not start with - (its CLI could parse
them as flags); the tool returns an actionable error instead of guessing.
Choosing models per agent
Model ids are agent-specific and do not overlap. o3 means nothing to
agy, gemini-3.6-flash-low means nothing to codex, and opencode namespaces
its own (opencode/big-pickle). So a single model value is valid for at most
one agent in a fan-out.
run_alltakesmodels— a per-agent map. Agents you don't list fall back tomodel, then to their own CLI default.review_changetakesrunnerModelandreviewerModel, so the agent writing the change and the agent judging it can use different engines and tiers.modelremains a fallback for both.
An unknown agent name in models is rejected with the list of enabled agents —
a typo never silently falls back to the default model.
Where to find valid ids: opencode models, cursor-agent models and
agy models list them. codex and claude have no such command — codex reads
its default from ~/.codex/config.toml, and claude accepts the documented
aliases (opus, sonnet, haiku, fable). Note claude models is not a
subcommand: it is treated as a prompt, so its "model list" is generated text,
not a source of truth.
Error handling
When a wrapped CLI fails, the hub classifies the failure and returns a clean,
ANSI-free, actionable isError result — never a raw terminal dump — naming the
class and the exact fix:
For example, an unauthenticated cursor no longer returns its ANSI "press any
key to sign in" banner — it returns cursor is not authenticated … Fix: run cursor-agent login``.
Review a change (review_change)
Runs a runner agent in a git cwd to make a change, captures the actual
git diff of what changed, then has a reviewer agent judge that diff. Returns
the runner's output, the diff (--stat), and a PASS / WARN / FAIL verdict
with findings.
Inputs: runner, reviewer (agent names), prompt, cwd (must be a git
worktree), optional runnerModel, reviewerModel, model (fallback for both),
timeoutMs.
Key notes:
-
Cross-agent by design — e.g.
codexwrites,claudereviews. -
Returns the concrete diff that the plain agent tools don't expose.
-
Newly-created (untracked) files are surfaced to the reviewer with their contents (bounded: 64 KiB per file, 50 files; excess is truncated and flagged).
git diffalone would omit them entirely. -
If the worktree was already dirty, the diff may include pre-existing changes (noted in the output).
-
Complements — does not replace — client-side stop-hooks or PR-time CI review.
-
The confirm gate (
MCP_CONFIRM) applies. -
The reviewer runs least-privilege — but how much that guarantees depends on the agent. The reviewer's prompt embeds an attacker-influenced diff, so it is run read-only rather than with the write grant the runner gets. Only two of the five are real restrictions:
Pick
codexorclaudeas the reviewer if you want the restriction to be real. This is defense-in-depth alongside the nonce-fenced diff and the throwaway temp cwd; none of it is a sandbox.
Prerequisites
Install and authenticate the CLIs you want to use (any subset works):
- Codex:
npm i -g @openai/codex && codex login - Cursor:
curl https://cursor.com/install -fsS | bash && cursor-agent login - OpenCode:
npm i -g opencode-ai && opencode auth login - Claude Code:
npm i -g @anthropic-ai/claude-code && claude(first run logs in) - Antigravity: install the Antigravity CLI (e.g.
brew install --cask antigravity-cli), then runagyonce and sign in — it has nologinsubcommand and stores credentials in the OS keyring, so there is no API-key env var to set
Install
Recommended — global install (fast, reliable startup): install the pinned
version once, then point your client at the agent-mcp-hub binary. Startup is
instant and the client connects reliably.
Claude Code
Cursor / generic mcp.json
Zero-install alternative (npx)
No global install, but npx re-resolves the package on every launch, so first start is slower and can occasionally trip a client's connection-probe timeout (the server itself is fine — just retry). Prefer the global install for a persistent setup.
Pre-release / fallback: To test an unreleased commit, run directly from GitHub:
npx -y github:blackaxgit/agent-mcp-hub#<tag-or-sha>. This builds from source on first fetch, so under npm v12+ you must allow thepreparescript.
Configuration
MCP_AGENTS — comma-separated allowlist of the agents to expose
(codex,cursor,opencode,claude,agy). Unset or empty exposes all agents. Disabled
agents get no tool and are absent from list_agents/run_all. An unknown name
fails at startup with an error listing the valid names, so typos never silently
disable an agent.
For stdio, set it in the client's mcp.json:
Confirm before running an agent — MCP_CONFIRM
Set MCP_CONFIRM=1 (values 1/true/on/all; default off) to require a
confirmation before any agent tool — and run_all — actually spawns a CLI. The
server sends a brief summary (agent · prompt · cwd · model) and waits: accept
runs the agent, decline runs nothing and returns a terminal cancellation.
This uses the standard MCP elicitation capability, so it is client/IDE-agnostic — it works with any MCP client that supports form elicitation (Claude Code, Cursor, VS Code, Zed, Windsurf, custom SDK clients, …); the gate keys on the protocol capability, never a product name. Clients that don't support elicitation transparently run without a prompt (no hang, no error).
Long-running tasks & timeouts
A complex agent task can run for many minutes. The hub bounds each run with two independent timers so a productive long run survives while a genuinely stuck one fails fast:
- Idle (inactivity) timeout —
idleTimeoutMs(per call) /MCP_AGENT_IDLE_TIMEOUT_MS(env), default 300000 (5 min). The timer resets on every chunk of output the CLI produces, so an agent that keeps working (streaming output) never trips it. An agent that goes silent — e.g.opencodestuck on an unreachable model backend — is killed after the idle window with an actionable "no output — the agent may be hung or its model/backend is unreachable" error, instead of burning the full cap. - Total runtime cap —
timeoutMs(per call) /MCP_AGENT_TIMEOUT_MS(env), default 1800000 (30 min). A hard upper bound regardless of activity.
Whichever fires first kills the agent's process group. Tradeoff: the idle reset
assumes the CLI streams intermediate output. codex and opencode do; claude -p,
cursor-agent -p and agy --print may emit only the final result, so a long
silent task on those can be idle-killed at 5 min — raise idleTimeoutMs /
MCP_AGENT_IDLE_TIMEOUT_MS for such tasks, or rely on the total cap.
agy is the strongest case here: it emits its entire answer in one flush at the
end (measured — every line of a 12-line reply arrived at the same instant), and
the hub raises its internal --print-timeout to 48h so that agy's own 5-minute
default can never truncate a run. The idle timer is therefore agy's only
protection against a genuine hang; budget idleTimeoutMs accordingly for long
autonomous agy tasks.
While an agent runs, the hub emits MCP progress notifications to clients that
request them (_meta.progressToken) — live feedback during long runs. Note: on
Claude Code (stdio) the per-server request timeout in .mcp.json (or the
MCP_TOOL_TIMEOUT env var it honors) is a hard wall-clock that progress does
not reset (default ~28h) — raise it if you lowered it below your longest run.
Upgrading
Global install: install the new version — the pinned agent-mcp-hub command
in your MCP config picks it up on the next client start:
npx (pinned): bump the pinned version in your MCP config — e.g. change
[email protected] to [email protected] everywhere.
Always-latest (not recommended for shared configs): use agent-mcp-hub@latest
instead of a pinned version. Note that npx caches by version — it may serve a
stale copy. Force a fresh fetch with npx --prefer-online agent-mcp-hub or
npx clear-npx-cache.
Pinning is reproducible and recommended for team-wide or checked-in
mcp.json files.
Development
Architecture
Pure adapters (src/adapters/* — prompt → {args, stdin?}, no I/O) → one
subprocess boundary (src/exec.ts) → MCP stdio server (src/server.ts). Adding
an agent = one ~15-line adapter file + one line in src/registry.ts.
License
Mozilla Public License 2.0 (MPL-2.0).
Versions before 0.5.2 were released under the MIT license; that grant stands for those versions. MPL-2.0 applies from 0.5.2 onward.
來源:README.md,提交 fb1e46a
工具
0版本歷史
2- v0.6.2最新Oct 1, 2026
- v0.6.1Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分