Loading...
The ACP to MCP adapter bridges ACP agents to MCP applications, enabling MCP tools to discover and run ACP agents as resources.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The ACP to MCP adapter bridges ACP agents to MCP applications, enabling MCP tools to discover and run ACP agents as resources.
The adapter allows MCP applications to run ACP agents, which can be risky depending on the agent's capabilities. It is relatively safe when using well-understood, read-only ACP agents. It becomes risky when agents have write or execute permissions, especially if the agent's behavior is not well-defined or trusted.
Performance is limited by the Stdio transport and the processing time of the ACP agents. Large inputs or complex agents may result in delays.
Cost depends on the resources consumed by the ACP agents. Consider the cost of API calls, tokens, and compute resources used by the agents.
uvx acp-mcp http://localhost:8000{
"mcpServers": {
"acp-local": {
"command": "uvx",
"args": ["acp-mcp", "http://localhost:8000"]
}
}
}run_agentInvokes a specified ACP agent with a given input.
The agent's actions depend on its implementation, which could include non-destructive writes.
None
hybrid
The adapter allows MCP applications to run ACP agents, which can be risky depending on the agent's capabilities. It is relatively safe when using well-understood, read-only ACP agents. It becomes risky when agents have write or execute permissions, especially if the agent's behavior is not well-defined or trusted.
Autonomy depends entirely on the ACP agent's implementation and the permissions granted within the MCP client. The adapter itself does not provide sandboxing or access control.
Production Tip
Monitor the performance and resource usage of ACP agents to ensure they do not negatively impact the MCP application.
It bridges ACP agents to MCP applications, allowing MCP tools to discover and run ACP agents.
ACP agents become MCP tools, there is no streaming, no shared memory, and only basic content translation.
Run the adapter with the ACP server URL as an argument (e.g., `uvx acp-mcp http://localhost:8000`).
Use the `use` command followed by the agent name and input (e.g., `use "echo" agent with the "Good morning!" input`).
Currently, only Stdio transport is supported.
No, the adapter does not provide sandboxing. Security depends on the ACP agent's implementation and the MCP client's permissions.
Error handling depends on the ACP agent and MCP client implementations. The adapter provides basic transport-level error reporting.