by gongrzhe
A2A Bridge enables agent discovery and task management by bridging Google's protocol with MCP, supporting shortest path
Connects MCP clients like Claude to Google's Agent-to-Agent (A2A) protocol agents, enabling cross-protocol communication between AI systems.
A2A Bridge is a community-built MCP server published by gongrzhe that provides AI assistants with tools and capabilities via the Model Context Protocol. A2A Bridge enables agent discovery and task management by bridging Google's protocol with MCP, supporting shortest path It is categorized under ai ml, developer tools. This server exposes 7 tools that AI clients can invoke during conversations and coding sessions.
You can install A2A Bridge in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
A2A Bridge is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
A2A Bridge is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
A2A Bridge is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend A2A Bridge for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired A2A Bridge into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
A2A Bridge is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
A2A Bridge is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: A2A Bridge surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, A2A Bridge benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
A2A Bridge has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: A2A Bridge is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 44
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.
This project serves as an integration layer between two cutting-edge AI agent protocols:
Model Context Protocol (MCP): Developed by Anthropic, MCP allows AI assistants to connect to external tools and data sources. It standardizes how AI applications and large language models connect to external resources in a secure, composable way.
Agent-to-Agent Protocol (A2A): Developed by Google, A2A enables communication and interoperability between different AI agents through a standardized JSON-RPC interface.
By bridging these protocols, this server allows MCP clients (like Claude) to discover, register, communicate with, and manage tasks on A2A agents through a unified interface.

also support cloud deployed Agent


Agent Management
Communication
Task Management
Transport Support
To install A2A Bridge Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @GongRzhe/A2A-MCP-Server --client claude
pip install a2a-mcp-server
Clone the repository:
git clone https://github.com/GongRzhe/A2A-MCP-Server.git
cd A2A-MCP-Server
Set up a virtual environment:
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
Install dependencies:
pip install -r requirements.txt
Configure how the MCP server runs using these environment variables:
# Transport type: stdio, streamable-http, or sse
export MCP_TRANSPORT="streamable-http"
# Host for the MCP server
export MCP_HOST="0.0.0.0"
# Port for the MCP server (when using HTTP transports)
export MCP_PORT="8000"
# Path for the MCP server endpoint (when using HTTP transports)
export MCP_PATH="/mcp"
# Path for SSE endpoint (when using SSE transport)
export MCP_SSE_PATH="/sse"
# Enable debug logging
export MCP_DEBUG="true"
The A2A MCP Server supports multiple transport types:
stdio (default): Uses standard input/output for communication
streamable-http (recommended for web clients): HTTP transport with streaming support
sse: Server-Sent Events transport
To specify the transport type:
# Using environment variable
export MCP_TRANSPORT="streamable-http"
uvx a2a-mcp-server
# Or directly in the command
MCP_TRANSPORT=streamable-http uvx a2a-mcp-server
# Using default settings (stdio transport)
uvx a2a-mcp-server
# Using HTTP transport on specific host and port
MCP_TRANSPORT=streamable-http MCP_HOST=127.0.0.1 MCP_PORT=8080 uvx a2a-mcp-server
Claude Desktop allows you to configure MCP servers in the claude_desktop_config.json file. This file is typically located at:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonAdd the following to the mcpServers section of your claude_desktop_config.json:
"a2a": {
"command": "uvx",
"args": [
"a2a-mcp-server"
]
}
Note that for Claude Desktop, you must use "MCP_TRANSPORT": "stdio" since Claude requires stdio communication with MCP servers.
If you've cloned the repository and want to run the server from your local installation:
"a2a": {
"command": "C:\path\ o\python.exe",
"args": [
"C:\path\ o\A2A-MCP-Server\a2a_mcp_server.py"
],
"env": {
"MCP_TRANSPORT": "stdio",
"PYTHONPATH": "C:\path\ o\A2A-MCP-Server"
}
}
Replace C:\path\ o\ with the actual paths on your system.
This repository includes a config_creator.py script to help you generate the configuration:
# If using local installation
python config_creator.py
The script will:
Here's an example of a complete claude_desktop_config.json file with the A2A-MCP-Server configured:
{
"mcpServers": {
"a2a": {
"command": "uvx",
"args": [
"a2a-mcp-server"
]
}
}
}
Claude can use A2A agents through the MCP tools provided by this server. Here's how to set it up:
For Claude Web: Start the MCP server with the streamable-http transport:
MCP_TRANSPORT=streamable-http MCP_HOST=127.0.0.1 MCP_PORT=8000 uvx a2a-mcp-server
For Claude Web: In Claude web interface, enable the MCP URL connection in your Tools menu.
http://127.0.0.1:8000/mcpFor Claude Desktop: Add the configuration to your claude_desktop_config.json file as described above. The easiest way is to use the provided config_creator.py script which will automatically detect paths and create the proper configuration.
In Claude, you can now use the following functions:
Register an A2A agent:
I need to register a new agent. Can you help me with that?
(Agent URL: http://localhost:41242)
Send message to an agent:
Ask the agent at http://localhost:41242 what it can do.
Retrieve task results:
Can you get the results for task ID: 550e8400-e29b-41d4-a716-446655440000?
Cursor IDE can connect to MCP servers to add tools to its AI assistant:
Run your A2A MCP server with the streamable-http transport:
MCP_TRANSPORT=streamable-http MCP_HOST=127.0.0.1 MCP_PORT=8000 uvx a2a-mcp-server
In Cursor IDE, go to Settings > AI > MCP Servers
http://127.0.0.1:8000/mcpNow you can use the A2A tools from within Cursor's AI assistant.
Windsurf is a browser with built-in MCP support:
Run your A2A MCP server with the streamable-http transport:
MCP_TRANSPORT=streamable-http MCP_HOST=127.0.0.1 MCP_PORT=8000 uvx a2a-mcp-server
In Windsurf browser, go to Settings > MCP Connections
http://127.0.0.1:8000/mcpYou can now use A2A tools from within Windsurf's AI assistant.
The server exposes the following MCP tools for integration with LLMs like Claude:
register_agent: Register an A2A agent with the bridge server
{
"name": "register_agent",
"arguments": {
"url": "http://localhost:41242"
}
}
list_agents: Get a list of all registered agents
{
"name": "list_agents",
"arguments": {}
}
unregister_agent: Remove an A2A agent from the bridge server
{
"name": "unregister_agent",
"arguments": {
"url": "http://localhost:41242"
}
}
send_message: Send a message to an agent and get a task_id for the response
{
"name": "send_message",
"arguments": {
"agent_url": "http://localhost:41242",
"message": "What's the exchange rate from USD to EUR?",
"session_id": "optional-session-id"
}
}
send_message_stream: Send a message and stream the response
{
"name": "send_message_stream",
"arguments": {
"agent_url": "http://localhost:41242",
"message": "Tell me a story about AI agents.",
"session_id": "optional-session-id"
}
}
get_task_result: Retrieve a task's result using its ID
{
"name": "get_task_result",
"arguments": {
"task_id": "b30f3297-e7ab-4dd9-8ff1-877bd7cfb6b1",
"history_length": null
}
}
cancel_task: Cancel a running task
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.