What it does
The bridge connects to one or more A2A agents, identified by their agent cards, and presents them to any MCP client as four tools: discover an agent, send it a message, read a task, and cancel a task. It translates message parts, artifacts, task states and errors between the two protocols, and reports the cases it cannot translate. Each reply carries the translated content together with a structured envelope, which holds the agent's data part, the task kind and opaque handles that the bridge issues in place of A2A identifiers.
It suits people who want MCP clients such as Claude Code or Cursor to talk to A2A agents without writing their own integration. For long-running work, a client that declares the MCP tasks extension receives a task handle as soon as the agent opens a task, then polls for status and can answer requests for input. Both the current MCP route and the legacy route are served on the same endpoint.
Running it requires Node 20 or later and a configuration file, agents.json, that lists each agent by alias and base URL or card URL. The bridge listens on a local loopback address and prints the MCP client configuration block on startup; Claude Code reads it from .mcp.json and Cursor from .cursor/mcp.json. The project is licensed under Apache-2.0.
Limitations and requirements
No authentication is provided on either side in this version. Only loopback hosts are accepted in Host and Origin headers unless allowedHosts is set in the configuration. In headless mode (claude -p) no one can answer an elicitation, so it is cancelled and the corresponding A2A task is cancelled too. Handles are held in memory and expire after fifteen minutes of non-use by default. MCP has no accepted-but-not-started state, so A2A SUBMITTED tasks appear as working. A2A free-text input requests are presented as a form with a single string field. Authorization requests (AUTH_REQUIRED) are not mapped to input_required, and without the result envelope they look the same as failures.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
A2A to MCP bridge
A2A v1.0.1 agents as MCP 2026-07-28 tools, with the tasks extension
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it