Happy slice of mcp pizzaMCP.pizza
Fire in da houseTop Tip:Paying $100+ per month for Perplexity, MidJourney, Runway, ChatGPT and other tools is crazy - get all your AI tools in one site starting at $15 per month with Galaxy AI Fire in da houseCheck it out free

MCP_A2A

MCP.Pizza Chef: regismesquita

MCP_A2A is a lightweight Python MCP server that enables Claude Desktop and other MCP clients to communicate with A2A protocol agents. It offers three core tools for registering servers, listing agents, and calling agents, facilitating rapid prototyping and integration of A2A-compatible agents. Designed primarily for developer experimentation rather than production deployment, it provides a flexible, hackable bridge to accelerate agent development workflows.

Use This MCP server To

Register and manage A2A protocol servers dynamically List all available A2A agents with their capabilities Send prompts to A2A agents and receive responses Integrate A2A agents into Claude Desktop or other MCP clients Rapidly prototype agent interactions without boilerplate code Experiment with agent-to-agent communication protocols

README

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.

Tools

The server provides three MCP tools:

  1. a2a_server_registry - Register or remove A2A servers

    {
  "action": "add", 
  "name": "security_audit", 
  "url": "http://localhost:8000"
}

  2. list_agents - List all registered agents with their capabilities

    {}

  3. call_agent - Send a prompt to an agent and get its response

    {
  "agent_name": "security_audit",
  "prompt": "regismesquita/DevControlMCP"
}

Workflow

The typical workflow is:

  1. Register an A2A server with a2a_server_registry
  2. List available agents with list_agents
  3. Call an agent with call_agent whenever 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.

Screenshot

image

MCP_A2A FAQ

How do I register a new A2A server with MCP_A2A?
Use the a2a_server_registry tool with an 'add' action, specifying the server name and URL to register it.
Can MCP_A2A be used in production environments?
MCP_A2A is designed primarily for development and prototyping; it is not recommended for production use without customization.
What tools does MCP_A2A provide?
It provides three tools: a2a_server_registry to manage servers, list_agents to view registered agents, and call_agent to interact with agents.
How does MCP_A2A facilitate agent communication?
It acts as a bridge allowing MCP clients like Claude Desktop to send prompts to and receive responses from A2A protocol agents.
Is MCP_A2A limited to Claude Desktop?
While optimized for Claude Desktop, MCP_A2A can work with any MCP client that supports its protocol.
How customizable is MCP_A2A?
The server is developer-friendly and hackable, allowing you to adapt and expand it to fit your needs.
What protocols or agent frameworks does MCP_A2A support?
It supports A2A protocol agents, particularly those built with pcingola/a2a_min and fast-agent.
How do I list all agents registered with MCP_A2A?
Use the list_agents tool, which returns all registered agents and their capabilities.