The ACP to MCP Adapter is a lightweight standalone server that acts as a bridge between two AI ecosystems: Agent Communication Protocol (ACP) for agent-to-agent communication and Model Context Protocol (MCP) for connecting AI models to external tools. It allows MCP applications (like Claude Desktop) to discover and interact with ACP agents as resources.
Key Features
- Makes ACP agents discoverable as MCP resources
- Exposes ACP agent runs as MCP tools
- Bridges two agent ecosystems with minimal configuration
Requirements
- Python 3.11 or higher
- Installed Python packages:
acp-sdk,mcp - An ACP server running (Tip: Follow the ACP quickstart to start one easily)
- An MCP client application (We use Claude Desktop in the quickstart)
Quickstart
1. Run the Adapter
Start the adapter and connect it to your ACP server:
uvx acp-mcp http://localhost:8000
[!NOTE] Replace
http://localhost:8000with your ACP server URL if different.
Prefer Docker?
docker run -i --rm ghcr.io/i-am-bee/acp-mcp http://host.docker.internal:8000
Tip: host.docker.internal allows Docker containers to reach services running on the host (adjust if needed for your setup).
2. Connect via Claude Desktop
To connect via Claude Desktop, follow these steps:
- Open the Claude menu on your computer and navigate to Settings (note: this is separate from the in-app Claude account settings).
- Navigate to Developer > Edit Config
- The config file will be created here:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- Edit the file with the following:
{
"mcpServers": {
"acp-local": {
"command": "uvx",
"args": ["acp-mcp", "http://localhost:8000"]
}
}
}
Prefer Docker?
{
"mcpServers": {
"acp-docker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/i-am-bee/acp-mcp",
"http://host.docker.internal:8000"
]
}
}
}
3. Restart Claude Desktop and Invoke Your ACP Agent
After restarting, invoke your ACP agent with:
use "echo" agent with the "Good morning!" input
Accept the integration and observe the agent running.
[!TIP] ACP agents are also registered as MCP resources in Claude Desktop.
To attach them manually, click the Resources icon (two plugs connecting) in the sidebar, labeled "Attach from MCP", then select an agent likeacp://agents/echo.
How It Works
- The adapter connects to your ACP server.
- It automatically discovers all registered ACP agents.
- Each ACP agent is registered in MCP as a resource using the URI:
acp://agents/{agent_name} - The adapter provides a new MCP tool called
run_agent, letting MCP apps easily invoke ACP agents.
Supported Transports
- Currently supports Stdio transport
Developed by contributors to the BeeAI project, this initiative is part of the Linux Foundation AI & Data program. Its development follows open, collaborative, and community-driven practices.
Metadata
Release files for acp-mcp 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| acp_mcp-0.4.2.tar.gz | 171.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acp_mcp-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 181.7 kB
Release files / acp_mcp-0.4.2.tar.gz
| Download URL | acp_mcp-0.4.2.tar.gz |
|---|---|
| Size | 171.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea41fbbdf8ebbb25d709641e8cec52dd7c8a1f4634c8967b798ff8ccbf3e3199
|
|
BLAKE2b-256 checksum How to use checksums |
f9d63c2ea4b36f880d15205a5b775915178a56deb49a34c2b8410edc0fa519a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 8, 2025.
Transparency logRelease files / acp_mcp-0.4.2-py3-none-any.whl
| Download URL | acp_mcp-0.4.2-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e03dece47224c224cf7713f859eb379305a330032e5a916fcedec79dcca94a8
|
|
BLAKE2b-256 checksum How to use checksums |
494b8d74099e28612833c0dee95b1bc3babab353d87cff1fb4a8854a997966c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 8, 2025.
Transparency log