MCP SERVERUse ACP agents from an MCP-compatible assistant to delegate tasks, route requests and continue interactive sessions.
No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.
ACP-MCP-Server connects agents using the Agent Communication Protocol (ACP) to assistants and other clients that support the Model Context Protocol (MCP), including Claude Desktop. It lets your assistant discover available agents, send them work and retrieve results, with support for requests that finish immediately, run asynchronously or pause for your input.
You run the bridge as a local process or a server, using stdio, SSE or Streamable HTTP to connect your client. Access is not read-only: its tools can start agent runs, resume waiting sessions and add routing rules.
When you have an ACP server but do not know which agents it offers, your assistant can discover them and retrieve details about a named agent. You can inspect the available choices before sending work.
Toolsdiscover_get_
When a task belongs with an existing ACP agent, send it from your MCP assistant by agent name. For work that takes longer, use asynchronous execution, check active runs and retrieve the result later using its run ID.
Toolsrun_list_get_
When different requests should go to different agents, use a routing strategy to select the recipient. You can inspect its rules, add keyword rules with priorities and preview which agent a request would select without executing it, then route the request for execution.
Toolslist_add_test_smart_
When an ACP agent needs answers during a task, an interactive session lets it pause for your response. Find waiting sessions and submit input to the relevant run so it can continue.
Toolsstart_list_provide_
When building an integration between ACP agents and an MCP client, inspect an ACP message's content types and structure, then convert it to an MCP-compatible format. This helps you examine the message and prepare it for the client.
Toolsanalyze_convert_
This tool list was captured on August 11, 2026 without a package version recorded; it may differ from the tools in your installed version.
Showing all 16
discover_acp_agentsFinds available ACP agents and registers them as resources in the bridge.
get_agent_infoRetrieves details about an ACP agent by name.
get_server_infoRetrieves information about the ACP-MCP bridge server.
get_async_run_resultRetrieves the result of an asynchronous agent run using its run ID.
list_active_runsLists active agent runs so you can see which executions are still in progress.
run_acp_agentRuns a named ACP agent on supplied text in synchronous or asynchronous mode.
add_routing_ruleAdds a rule to a routing strategy, with keywords, a target agent and an optional priority.
list_routing_strategiesLists available routing strategies and their rules so you can inspect how requests are assigned to agents.
smart_route_requestRoutes a text request to an ACP agent using a chosen routing strategy.
test_routingShows which agent a routing strategy would select for a request without executing the agent.
cancel_interactionCancels a pending interactive agent run identified by its run ID.
list_pending_interactionsLists interactive agents waiting for user input, helping you find sessions that need a response.
provide_user_inputSends user input to a waiting interactive agent run and resumes it, using its run ID.
start_interactive_agentStarts a named ACP agent with an initial message for an interaction that may pause for user input.
analyze_message_contentExamines an ACP message’s content types and structure to help inspect what the message contains.
convert_acp_messageConverts an ACP message into an MCP-compatible format.
No matching results.
Set up the bridge for your MCP client with Python 3.11+ and a running ACP server with agents.
You need Python 3.11+ and uvx on PATH. Have an ACP server with agents running at http://localhost:8000, the default address used by this configuration.
In Claude Desktop, open Settings > Developer > Edit Config. Add the configuration below and save the JSON file. If it already contains an mcpServers object, add the acp-bridge entry inside it, keeping your existing server entries.
claude_desktop_config.jsonJSON{
"mcpServers": {
"acp-bridge": {
"command": "uvx",
"args": ["acp-mcp-server"]
}
}
}Completely quit Claude Desktop, then reopen it to load the configuration and start the bridge.
Check the result
Check that the bridge’s tools appear
At the bottom-left of the conversation input box, click “Add files, connectors, and more /”, then open Connectors > Manage connectors. Select acp-bridge and check that its available tools are listed.
ACP-MCP-Server setup and requirementsConnect local MCP servers to Claude Desktop