Summary
Protocol plumbing that comes with the routing logic that makes it worth installing.
A bridge on its own would be unremarkable; the routing layer is the reason to look, with strategies built from keywords and priorities and a dry-run tool that shows the decision before anything executes. The interactive path is the other thing worth knowing about, since agents that stop to ask a question are what usually breaks when one protocol is wrapped inside another.
What it is
A bridge between the Agent Communication Protocol and MCP, with 16 tools covering agent discovery, execution modes, message-format conversion, rule-based routing and interactive sessions.
What you get
- ACP agents discovered and registered as resources, with per-agent detail available afterwards
- An agent run by name in a chosen mode, carrying a session id across calls
- Asynchronous runs tracked by run id, with an active-run list and results collected when they finish
- Requests routed by strategy instead of by name, with routing rules added from keywords and priorities
- Routing tested without execution — the tool reports which agent would have been selected
- Interactive agents that pause for input: a pending list, an input call keyed by run id, a timeout in minutes, and cancellation
- ACP messages converted to MCP-compatible format, and their content types and structure analysed
Requirements
ACP agents already running for the discovery call to find — every execution and routing tool addresses an agent by the name discovery returns.
Setup effort
One command — uvx acp-mcp-server