A2A MCP Server
Used to build the web interface for monitoring agent status and tracking connected agents in the MCP server implementation
Provides the core runtime environment for both the MCP server and agent implementations, supporting both centralized and peer-to-peer communication models
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 Serverlist all connected agents and their current status"
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 Agents
This project demonstrates two different approaches to agent communication:
Master Control Program (MCP) - A centralized server-based approach where agents communicate through a central server
Agent-to-Agent (A2A) - A decentralized peer-to-peer approach where agents communicate directly with each other
Installation
Create and activate a virtual environment:
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activateInstall dependencies:
pip install -r requirements.txtRelated MCP server: Novu MCP Server
Usage
MCP Server and Agents
Start the MCP server:
python cli.py run-mcp-serverIn separate terminals, start one or more MCP agents:
python cli.py run-mcp-agent --agent-id agent1
python cli.py run-mcp-agent --agent-id agent2The MCP server will track all connected agents and their status. You can view the status by opening http://localhost:5000 in your browser.
A2A (Agent-to-Agent) Network
Start the first A2A agent:
python cli.py run-a2a-agent --agent-id a2a1 --port 5001Start additional A2A agents, connecting them to existing agents:
python cli.py run-a2a-agent --agent-id a2a2 --port 5002 --peer localhost:5001
python cli.py run-a2a-agent --agent-id a2a3 --port 5003 --peer localhost:5001 --peer localhost:5002A2A agents will automatically discover other agents through their initial peers. You can type messages in any agent's terminal to broadcast them to all connected agents.
Architecture
MCP (Master Control Program)
Centralized server that tracks all agents
Agents register with the server and maintain connection through heartbeats
Server provides a web interface to monitor agent status
Simple and reliable but has a single point of failure
A2A (Agent-to-Agent)
Decentralized peer-to-peer network
Agents connect directly to each other
Messages are flooded through the network
More resilient but requires more complex coordination
No single point of failure
Project Structure
a2a_mcp/
├── agents/ # Agent implementations
│ ├── mcp_agent.py # MCP-based agent
│ └── a2a_agent.py # Peer-to-peer agent
├── mcp/ # MCP server implementation
│ └── server.py # Flask-based MCP server
├── cli.py # Command-line interface
└── requirements.txt # Python dependenciesContributing
Feel free to submit issues and pull requests to improve the demonstration.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/khulnasoft-com/a2a-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server