Cli MCP Server

Other AI CLIs (Gemini, GPT, Claude, opencode, Ollama) as a council — ban-safe, no API keys. That is what the cli mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

You're talking to one AI assistant. You've also installed and logged into others — Claude Code, Codex, Gemini, opencode, Ollama. cli-bridge connects them: when your assistant needs something it can't do alone, it asks one of the other CLIs and hands you the result.

• 🛡️ Ban-safe by design. It spawns each model's official CLI, exactly as you'd run it by hand —
• 💸 Cost-safe defaults you tune to your plan. Out of the box ask_all / ask_cascade build a
• 🔌 Works from any host. Claude Code, Codex, opencode, Cursor, VS Code (Cline/Continue), Zed —
• 🧭 The cross-vendor edge is the moat. Independent verification means a different vendor in the

The tools it exposes

The server publishes 4 tools. What each one is for:

• Superpower — Which CLI has it
• Images — Codex (gpt-image-2, no API key — paid ChatGPT plan, not Free)
• Vision — images=[…] on Codex · opencode · Ollama · Apple · Gemini ⚗️
• Hosts — Claude Code-first (plugin; MCP server secondary)

Getting it running

The server ships on PyPI as cli-bridge-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: CLI_BRIDGE_HIDE_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cli's toolset — Superpower, Images, Vision and 1 more — is a fair guide to whether it matches your workflow. It is maintained by JoaoBerne; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cli's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.