Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@A2A MCP Servercall the security audit agent to review my latest code changes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A2A MCP Server
A simple MCP server that provides Claude Desktop access to A2A protocol agents.
Developer friendly more than production ready, you can hack it to adapt to your needs and expand on whatever you need. But probably not the best idea to deploy into prod as-is.
Overview
This project was created to connect Claude Desktop with A2A (Agent-to-Agent) protocol agents, particularly those built with pcingola/a2a_min and fast-agent. It was developed as a personal project to assist with agent development and for fun.
Related MCP server: MCP Tool
Tools
The server provides three MCP tools:
a2a_server_registry - Register or remove A2A servers
{ "action": "add", "name": "security_audit", "url": "http://localhost:8000" }list_agents - List all registered agents with their capabilities
{}call_agent - Send a prompt to an agent and get its response
{ "agent_name": "security_audit", "prompt": "regismesquita/DevControlMCP" }
Workflow
The typical workflow is:
Register an A2A server with
a2a_server_registryList available agents with
list_agentsCall an agent with
call_agentwhenever needed
Local Testing
This server has been tested locally with a security audit agent built on fast-agent and a2a_min. It successfully enables Claude Desktop to communicate with A2A agents.
Purpose
This bridge allows Claude Desktop to interact with any A2A-compatible agent, extending Claude's capabilities through the MCP tools interface.