kagero
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kageroRun 'explain this repository' using the mcode backend"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
kagero
Kagero — one Agent interface over coding-agent CLIs, exposed as an MCP
server and a CLI. Ten backends, seven honest tools, zero pretending: whatever a
backend cannot do comes back as an explicit [unsupported_capability] error,
never as a guess.
Backends
backend | transport | binary |
| in-process SDK ( | — |
| subprocess, |
|
| subprocess, |
|
| long-lived subprocess, live |
|
| subprocess, |
|
| subprocess, |
|
| subprocess, grok ACP + streaming print |
|
| subprocess, |
|
| subprocess, |
|
| subprocess, |
|
Select with KAGERO_BACKEND or kagero mcp --backend=<name>; kagero backends
lists what is registered.
Related MCP server: all-agents-mcp
Install
npm install kagero-mcp
# or run without installing
npx kagero-mcpThe pi-sdk backend needs its optional peer dependency:
npm install @earendil-works/pi-coding-agentUsage
CLI
kagero prompt "List the files in the current directory" # one-shot
KAGERO_BACKEND=mcode kagero prompt "…" # pick a backend
kagero backends # registered backends
kagero models # active backend models
kagero sessions # persistent sessions
kagero mcp --backend=mcode # MCP server over stdioMCP tools
run (fresh prompt, or continue a session via session_id; blocking or
run_in_background), send_message (steer / follow_up / abort),
task_list, task_output, task_stop (the background-run registry),
history, info.
A background run returns {task_id, status: "running"} immediately; when it
finishes a task-completed logging notification announces the outcome and
task_output returns the final result.
History
history returns a compact normalized view, paged from the newest end
(page / page_size, entry indexes are global across pages) with a
full-log pointer. Readers for pi, qwen, grok, kimi, mcode (MiniMax Code),
claude, codex and dsh parse each CLI's on-disk session logs, capture
thinking blocks and merge tool results into their calls.
Session compression (optional)
Set KAGERO_COMPRESS_BACKEND (and optionally KAGERO_COMPRESS_MODEL) to
enable run reports and the compressed live stream: agent event streams are
compressed by a cheap second agent into anchored, machine-validated digests —
per-move blocks with distilled reasoning, a rolling checkpoint and a status
verdict. history prepends the digest header when one exists and
task_output (include_blocks) returns the compressed blocks. Compressed
state persists across restarts in a crash-safe journal (~/.kagero/watch/).
Architecture
Agent interface (@kagero/core)
├─ CliSpecAgent (@kagero/cli-backend) — spec-driven print/ACP transports,
│ history readers, stream-json parsers
├─ PiSdkAgent / PiRpcAgent (@kagero/pi-backend)
├─ ClaudeStreamAgent (@kagero/cli-backend) — live stream-json protocol
└─ createKageroMcpServer (@kagero/mcp) — MCP factory over any registrySee docs/ARCHITECTURE.md for the full contract.
Security & behavior
Strict schemas. Every tool input is enforced with
z.object(...).strict(); unknown fields are rejected before they reach a backend.Honest statuses. Runs end
completed,aborted,timed-outor with the CLI's own error — a killed run is never success.Fail-closed permissions. Live transports answer reverse permission requests with an explicit deny; nothing is auto-approved headlessly.
No resource leaks. Process groups are killed through a SIGTERM → grace → SIGKILL ladder; ACP clients outlive single runs and are disposed on shutdown.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Related MCP Servers
- AlicenseAqualityFmaintenanceProvides unified access to multiple CLI AI agents (Codex, Gemini, Claude, and OpenCode) through a single MCP interface with real-time task monitoring, enabling specialized code analysis, UI design, implementation, and prototyping workflows.1121MIT
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.144 npm14MIT
- AlicenseNot gradedqualityDmaintenanceUnified CLI multiplexer for AI coding agents, enabling orchestration of multiple coding CLI tools through a single interface with session persistence, cost tracking, and MCP tool support.13 npm19MIT
- AlicenseAqualityAmaintenanceBridges multiple CLI coding agents (Codex, Cursor, OpenCode, Claude, Antigravity) into any MCP client, enabling delegation of prompts, parallel execution, and code review workflows.633 npmMozilla Public 2.0