Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @osanoai/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add osanoai-multicli -- npx -y @osanoai/multicli@1.5.41In einem Terminal ausführen.
{ "mcpServers": { "osanoai-multicli": { "command": "npx", "args": [ "-y", "@osanoai/[email protected]" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
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.
StartenAn MCP server that lets Claude, Antigravity, Codex, and OpenCode call each other as tools.
Claude: "Hey Antigravity, what do you think about this code?"
Antigravity: "It's messy. Let me ask Codex for a second opinion."
Codex: "You're both wrong. Here's the fix."
OpenCode: "I checked with three providers. They all agree with Codex."
curl -fsSL https://raw.githubusercontent.com/osanoai/multicli/main/install.sh | bash
Detects which AI CLIs you have installed and configures Multi-CLI for them automatically.
127.0.0.1Multi-CLI sits between your AI clients and bridges them via the Model Context Protocol. Install it once, and whichever AI you're talking to gains the ability to call the others.
This tool was built by the very AIs it connects.
Claude, Codex, Gemini, and OpenCode wrote the code. Claude, Codex, Gemini, and OpenCode maintain it. Every night, a CI job queries the latest stable release of the static-catalog CLIs for current model lists, diffs the results against what's in the repo, and automatically publishes a new version if anything changed. Antigravity models are discovered live through agy models because that command depends on local sign-in and account access.
The stdio install paths use @latest, so those clients pick up new releases automatically. Claude Code's managed HTTP service intentionally runs from a stable installed runtime instead of a transient npx cache; rerun the installer or multicli service refresh --configure-claude after upgrading.
Most MCP tools go stale within weeks. This one is self-maintaining by design.
You need Node.js >= 20 and at least one of these CLIs installed:
Multi-CLI is most useful with two or more CLIs installed. With only one, the install still works, but there may be nothing to bridge yet.
Prefer to install per-client yourself? Each command is one line.
Recommended for Claude Code stability:
npm install -g @osanoai/multicli
multicli service install --configure-claude
This installs a per-user background service that listens only on 127.0.0.1, configures Claude Code to use Multi-CLI over HTTP, and keeps the underlying server alive even if Claude drops a stdio subprocess.
The managed service installs as a per-user login/background service:
launchd LaunchAgentsystemd --userSecurity model:
127.0.0.1Authorization: Bearer <token> for every HTTP MCP requestOperational notes:
multicli service install refuses transient npx runtimes; use a global install or a stable local checkoutsystemd --user service follows your login session; enable linger yourself only if you intentionally want it to stay up after logoutLegacy stdio installation is still available:
claude mcp add --scope user Multi-CLI -- npx -y @osanoai/multicli@latest
Add to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS:
{
"mcpServers": {
"Multi-CLI": {
"command": "npx",
"args": ["-y", "@osanoai/multicli@latest"]
}
}
}
Restart Claude Desktop completely after saving.
mkdir -p ~/.gemini/config
node -e 'const fs=require("fs"),p=process.env.HOME+"/.gemini/config/mcp_config.json";let c={};if(fs.existsSync(p)){c=JSON.parse(fs.readFileSync(p,"utf8")||"{}")}c.mcpServers={...(c.mcpServers||{}),"Multi-CLI":{command:"npx",args:["-y","@osanoai/multicli@latest"]}};fs.writeFileSync(p,JSON.stringify(c,null,2)+"\n")'
{
"mcpServers": {
"Multi-CLI": {
"command": "npx",
"args": ["-y", "@osanoai/multicli@latest"]
}
}
}
codex mcp add Multi-CLI -- npx -y @osanoai/multicli@latest
codex --mcp-config mcp.json
Where mcp.json contains:
{
"mcpServers": {
"Multi-CLI": {
"command": "npx",
"args": ["-y", "@osanoai/multicli@latest"]
}
}
}
OpenCode's mcp add command is interactive, so add Multi-CLI to ~/.config/opencode/opencode.json directly:
{
"mcp": {
"Multi-CLI": {
"type": "local",
"command": ["npx", "-y", "@osanoai/multicli@latest"]
}
}
}
If the file already exists, merge the "Multi-CLI" entry into the existing "mcp" object.
Multi-CLI supports both stdio and Streamable HTTP.
For stdio-capable clients, point them at:
npx -y @osanoai/multicli@latest
For a managed local HTTP service, install Multi-CLI globally and run:
multicli service install
The service listens on 127.0.0.1 only and exposes /mcp plus /health.
Once connected, your AI client gains access to tools for the other CLIs (never its own):
The Ask-* tools still work as normal synchronous MCP tools, but they now also advertise optional task-based execution for MCP clients that support tasks.
Ask-* calls using MCP tasks to avoid long blocking tool requestsAsk-* tools synchronously with no config changesList-*, *-Help, and Fetch-Chunk remain normal synchronous toolsOnce installed, just talk naturally to your AI:
"Ask-Antigravity what it thinks about this architecture"
"Have Codex review this function for performance issues"
"Get Claude's opinion on this error message"
"Use OpenCode to get a second opinion from Llama"
Or get a second opinion on anything:
"I want three perspectives on how to refactor this module —
ask Antigravity and Codex what they'd do differently"
┌─────────────┐ MCP (stdio) ┌──────────────┐ CLI calls ┌─────────────┐
│ Your AI │ ◄──────────────────► │ Multi-CLI │ ───────────────► │ Other AIs │
│ Client │ │ server │ │ (CLI tools) │
└─────────────┘ └──────────────┘ └─────────────┘
1. Your AI client connects to Multi-CLI via MCP
2. Multi-CLI detects which CLIs are installed on your system
3. It registers tools for the OTHER clients (hides tools for the calling client)
4. When a tool is called, Multi-CLI executes the corresponding CLI command
5. Results flow back through MCP to your AI client
For Claude Code, Multi-CLI can also run as a local background HTTP service:
┌─────────────┐ MCP (HTTP) ┌──────────────┐ CLI calls ┌─────────────┐
│ Claude Code │ ◄──────────────────► │ Multi-CLI │ ───────────────► │ Other AIs │
│ Client │ 127.0.0.1 only │ service │ │ (CLI tools) │
└─────────────┘ └──────────────┘ └─────────────┘
"No usable AI CLIs detected" Make sure at least one other CLI is installed and on your PATH:
which agy && which codex && which claude && which opencode
No tools showing up? If only your own CLI is installed, Multi-CLI hides it (no self-calls). Install a different CLI to enable cross-model collaboration.
MCP server not responding?
npx -y @osanoai/multicli@latest directly to see if the stdio server startsClaude Code disconnecting after successful calls? Use the managed background service instead of the legacy stdio integration:
npm install -g @osanoai/multicli
multicli service install --configure-claude
multicli service doctor
Helpful service commands:
multicli service statusmulticli service doctormulticli service logsmulticli service refreshmulticli service uninstallNeed to tune timeouts or cleanup behavior? Multi-CLI supports these optional environment variables:
MULTICLI_TRANSPORT (stdio or http)MULTICLI_ASK_TIMEOUT_MSMULTICLI_HELP_TIMEOUT_MSMULTICLI_CLI_DETECT_TIMEOUT_MSMULTICLI_KILL_GRACE_MSMULTICLI_HTTP_HOST (defaults to 127.0.0.1)MULTICLI_HTTP_PORT (defaults to 37420)MULTICLI_HTTP_PATH (defaults to /mcp)MULTICLI_HTTP_AUTH_TOKEN (required for direct HTTP mode)MULTICLI_HTTP_SESSION_IDLE_MSMULTICLI_LOG_PATH (defaults to ~/.multicli/logs/multicli.log)MULTICLI_LOG_LEVEL (error, info, or debug; defaults to debug for the file log)MULTICLI_STDERR_LOG_LEVEL (silent, error, info, or debug; defaults to error)MULTICLI_SERVICE_ROOT_DIRMULTICLI_SERVICE_LOG_PATHMULTICLI_SERVICE_ENV_PATHMULTICLI_SERVICE_MANIFEST_PATHThe server writes structured JSON-line logs to a single file destination, rotates them automatically for long-running service mode, and includes full prompt bodies for Ask-* requests so disconnects and crashes can be reconstructed after the fact.
git clone https://github.com/osanoai/multicli.git
cd multicli
npm install
npm run build
npm run dev
MCP server for Multiple CLI coding agent integration (Claude + Antigravity + Codex)
{ "mcpServers": { "osanoai-multicli": { "command": "npx", "args": [ "-y", "@osanoai/[email protected]" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
@osanoai/multicli läuft lokal über stdio.
Zuletzt geprüft: 2026-11-15. MCP server for Multiple CLI coding agent integration (Claude + Antigravity + Codex)