A mcp server that bridges the Model Context Protocol (MCP) with the Agent-to-Agent (A2A) protocol, enabling MCP-compatible AI assistants (like
A mcp server that bridges the Model Context Protocol (MCP) with the Agent-to-Agent (A2A) protocol, enabling MCP-compatible AI assistants (like Claude) to seamlessly interact with A2A agents. That is what the a2a mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This project serves as an integration layer between two cutting-edge AI agent protocols:
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 2 tools. What each one is for:
Demo — The Demo tool exposed by this serverClaude — Claude can use A2A agents through the MCP tools provided by this server. Here's how to set it up:Configuration is passed through the environment: MCP_TRANSPORT, PYTHONPATH, MCP_HOST, MCP_PORT, MCP_PATH, MCP_SSE_PATH, MCP_DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. A2A's toolset — Demo, Claude — is a fair guide to whether it matches your workflow. It is maintained by GongRzhe; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Demo | The Demo tool exposed by this server. |
| Claude | Claude can use A2A agents through the MCP tools provided by this server. Here's how to set it up: |
{
"mcpServers": {
"a2a": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"MCP_TRANSPORT": "your-value",
"PYTHONPATH": "your-value",
"MCP_HOST": "your-value",
"MCP_PORT": "your-value",
"MCP_PATH": "your-value",
"MCP_SSE_PATH": "your-value",
"MCP_DEBUG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT | Configuration value read at startup. | Optional |
| PYTHONPATH | Filesystem location the server is allowed to use. | Optional |
| MCP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_PORT | Configuration value read at startup. | Optional |
| MCP_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_SSE_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_DEBUG | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.