Multi-Component System with A2A and MCP Server Integration

Name: Multi-Component System with A2A and MCP Server Integration
Author: BulloRosso

@BulloRosso

代码仓库

关于 Multi-Component System with A2A and MCP Server Integration

An agent playground (without authentication) in a single repo for fastest turn around cycles during experiments.

#react #ai #mcp-server #mcp-client #a2a-protocol

基本信息

分类

其他

许可证

MIT license

运行时

node

传输方式

stdio

发布者

BulloRosso

配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块，请前往代码仓库查看安装说明。

代码仓库

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Multi-Component System with A2A and MCP Server Integration?

A scalable multi-component system built with modern web technologies. It integrates a React/TypeScript frontend, a Python/FastAPI backend API, a Node.js proxy server, an A2A (Agent-to-Agent) server following Google’s A2A protocol, and an MCP (Model Context Protocol) server implementing Anthropic’s protocol. Designed for developers building agent-based applications with real-time communication and modular architecture.

How to use Multi-Component System with A2A and MCP Server Integration?

Install prerequisites (Node.js 20+, Python 3.11+, npm or yarn). Run each service in its own process: API Backend (cd api; pip install -r requirements.txt; python main.py), Frontend (cd frontend; npm install; npm run dev), Proxy Server (node proxy-server.js), A2A Server (cd a2a-server; node simple-server.js), and MCP Server (cd mcp-server; pip install -r requirements.txt; python mcp_server.py). Integration tests are available in the tests directory.

Key features of Multi-Component System with A2A and MCP Server Integration

React/TypeScript frontend with Material-UI and Zustand state management
Python/FastAPI backend with health check and API documentation
Node.js reverse proxy routing requests to appropriate services
A2A server enabling agent-to-agent task and message exchange
MCP server providing tools, resources, and prompts with SSE support
WebSocket support for real-time communication

Use cases of Multi-Component System with A2A and MCP Server Integration

Building agent-based applications that communicate via the A2A protocol
Exposing tools, resources, and prompt templates through the MCP protocol
Creating a dashboard with real-time data streaming via SSE
Developing a scalable multi-service architecture with a central proxy
Running integration tests for agent communication flows

FAQ from Multi-Component System with A2A and MCP Server Integration

What are the prerequisites for running this system?

Node.js 20+ and Python 3.11+ are required. npm or yarn must be installed.

How do I run the application?

Each service must be run in its own process: the API backend, frontend dev server, proxy server, A2A server, and MCP server. See the “Running the Application” section in the README for detailed commands.

Are there tests available?

Yes, integration tests for the A2A server are located in the tests directory and can be run with node run-tests.js.

What endpoints does the MCP server provide?

The MCP server exposes endpoints for status, tools, resources, prompts, and an SSE event stream. Both direct (/status) and SSE-prefixed (/sse/status) paths are available.

How are requests routed between components?

A Node.js proxy server routes frontend requests to the Vite dev server, API requests to FastAPI, A2A requests to the A2A server, and MCP/SSE requests to the MCP server.