Mcacp
Run ACP-compatible coding agents from Claude Desktop, Cursor, or any MCP host without swapping clients.
Overview
io.github.Oortonaut/mcacp is an MCP server for the Build phase that bridges MCP clients to ACP coding agents over stdio.
What is this MCP server?
- Stdio MCP server (npm package mcacp v0.1.3) exposing an MCP-to-ACP bridge
- Lets any MCP client drive ACP coding agents from one config block
- Published on GitHub (Oortonaut/mcacp) with Model Context Protocol server schema
- No extra env vars in server.json—install and point your host at the stdio command
- Pairs with task-graph-mcp when you want governed workflows on top of ACP agents
- Server version 0.1.3 on npm identifier mcacp
- Single stdio transport package in server.json
- GitHub repository Oortonaut/mcacp
Community signal: 5 GitHub stars.
What problem does it solve?
Your MCP host can call tools and read files, but it cannot natively start or control ACP coding agents without a separate client or custom glue.
Who is it for?
Solo builders already on MCP who want to pilot ACP coding agents without abandoning Claude Code or Cursor.
Skip if: Teams that only need static API wrappers, geocoding, or OSINT lookups with no ACP agent backend.
What do I get? / Deliverables
After you add mcacp, the same MCP configuration can drive ACP agent sessions so implementation stays inside your current agent workflow.
- MCP tools that forward work to ACP coding agents
- Unified agent config without a second ACP-only desktop app
- Repeatable stdio MCP entry for local agent sessions
Recommended MCP Servers
Journey fit
Agent bridges land in Build because they wire your IDE or chat client to external coding agents during implementation. Canonical shelf is agent-tooling: it translates MCP tool calls into ACP sessions rather than shipping app features directly.
How it compares
Protocol bridge MCP server, not a workflow graph or standalone agent skill.
Common Questions / FAQ
Who is io.github.Oortonaut/mcacp for?
Indie and solo developers who use MCP daily and want ACP coding agents callable from that same host.
When should I use io.github.Oortonaut/mcacp?
Use it during Build when connecting your editor’s MCP client to an ACP agent runtime for delegated coding tasks.
How do I add io.github.Oortonaut/mcacp to my agent?
Install the npm package mcacp (v0.1.3), add a stdio MCP server entry pointing at that binary, and restart your MCP-capable client.