a2a-mcp-bridge
Bridges MCP clients (like Claude Desktop) to A2A agents, enabling message sending and agent card retrieval via a stateless, non-persistent server.
README
a2a-mcp-bridge
A minimal MCP server that bridges MCP clients
(Claude Desktop, etc.) to A2A agents — built directly on
a2a-sdk 0.3.26+, so it speaks the A2A
protocol version that current agent servers (e.g. Google ADK's to_a2a) actually
implement.
Stateless by design: no registry file, no local persistence, nothing written to disk. Each call opens a connection, does the round trip, and returns — so it never hits the file-permission traps that registry/cache-based bridges run into on locked-down or sandboxed clients.
Why this exists
The most visible community bridge, PyPI's a2a-mcp-server, does not depend on
a2a-sdk at all — it vendors a hand-copied client from the pre-1.0 draft A2A
protocol. Its hardcoded JSON-RPC methods are tasks/send, tasks/sendSubscribe,
tasks/get, tasks/cancel, tasks/pushNotification/{get,set}.
Current a2a-sdk (0.3.26+) servers use a different method set entirely:
message/send, message/stream, tasks/get, tasks/cancel,
tasks/pushNotificationConfig/{get,set,list,delete}, tasks/resubscribe,
agent/getAuthenticatedExtendedCard.
Point the old bridge at a modern A2A server and every call fails with
-32601 Method not found — the server has genuinely never heard of tasks/send.
This isn't a version skew you can fix by bumping a pin; the dialect changed.
a2a-mcp-bridge sidesteps the problem by using a2a-sdk's own client
(ClientFactory, send_message), so it always speaks whatever protocol the SDK
you install implements.
Install
Option A — uvx, no clone, no install:
uvx --from git+https://github.com/ytugarev/a2a-mcp-bridge a2a-mcp-bridge
Option B — pip, from source:
git clone https://github.com/ytugarev/a2a-mcp-bridge
cd a2a-mcp-bridge
pip install -e .
Option C — single file, zero install: src/a2a_mcp_bridge/server.py carries a
PEP 723 inline metadata header, so you can
download that one file and run it directly with uv — uv resolves and caches
its dependencies on first launch, no pip install and no venv to manage:
uv run --script /absolute/path/to/server.py
Configure
Two environment variables, both optional:
| Variable | Default | Purpose |
|---|---|---|
A2A_AGENT_URL |
http://localhost:8001 |
Default A2A agent endpoint (also overridable per tool call) |
A2A_TIMEOUT_SECONDS |
300 |
HTTP client timeout — raise this for slow/long-running agents |
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"a2a-bridge": {
"command": "a2a-mcp-bridge",
"env": {
"A2A_AGENT_URL": "http://192.168.1.50:8001"
}
}
}
}
Using the single-file uv run --script form instead (Option C above):
{
"mcpServers": {
"a2a-bridge": {
"command": "/absolute/path/to/uv",
"args": ["run", "--script", "/absolute/path/to/server.py"],
"env": {
"A2A_AGENT_URL": "http://192.168.1.50:8001"
}
}
}
}
Both command and every path in args must be absolute. MCP clients launch
server subprocesses with the working directory set to some system default (on
Windows, Claude Desktop uses C:\WINDOWS\System32) and often a stripped PATH,
so a bare "uv" or a relative "server.py" will silently fail to resolve —
this is the single most common setup error with this bridge (and MCP servers in
general), not a bug in the bridge itself. On Windows, also double check your
actual config path: Store-installed Claude Desktop keeps it under
AppData\Local\Packages\<package-id>\LocalCache\Roaming\Claude\, not the
%APPDATA%\Claude path most docs assume.
Tools exposed
get_agent_card(agent_url?)— fetches the target agent's name, description, and skills from its/.well-known/agent.jsoncard.send_a2a_message(message, agent_url?)— sends a message to the agent and returns its final text response. Runs non-streaming so the client gets one clean answer per call, even if the underlying agent takes minutes.
Both tools accept an optional agent_url override, so a single bridge
instance can talk to multiple agents if needed.
Requirements
- Python 3.10+
- An A2A server speaking
a2a-sdk0.3.26+ semantics (e.g. Google ADK'sto_a2a, or anything else built on the same SDK)
Development
pip install -e ".[dev]"
pytest
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。