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
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:
Install dependencies:
Related MCP server: Playwright MCP Server
Usage
MCP Server and Agents
Start the MCP server:
In separate terminals, start one or more MCP agents:
The 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:
Start additional A2A agents, connecting them to existing agents:
A2A 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
Contributing
Feel free to submit issues and pull requests to improve the demonstration.