A2AMCP
A Redis-backed MCP server that enables multiple AI agents to communicate, coordinate, and collaborate while working on parallel development tasks, preventing conflicts in shared codebases.
README
A2AMCP - Agent-to-Agent Model Context Protocol
Enabling Seamless Multi-Agent Collaboration for AI-Powered Development
A2AMCP brings Google's Agent-to-Agent (A2A) communication concepts to the Model Context Protocol (MCP) ecosystem, enabling AI agents to communicate, coordinate, and collaborate in real-time while working on parallel development tasks.
Originally created for SplitMind, A2AMCP solves the critical problem of isolated AI agents working on the same codebase without awareness of each other's changes.
✅ Server Status: WORKING! All 17 tools implemented and tested. Uses modern MCP SDK 1.9.3.
🚀 Quick Start
Using Docker (Recommended)
# Clone the repository
git clone https://github.com/webdevtodayjason/A2AMCP
cd A2AMCP
# Start the server
docker-compose up -d
# Verify it's running
docker ps | grep splitmind
# Test the connection
python verify_mcp.py
Configure Your Agents
Claude Code (CLI)
# Add the MCP server using Claude Code CLI
claude mcp add splitmind-a2amcp \
-e REDIS_URL=redis://localhost:6379 \
-- docker exec -i splitmind-mcp-server python /app/mcp-server-redis.py
Claude Desktop
Add to your configuration file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"splitmind-a2amcp": {
"command": "docker",
"args": ["exec", "-i", "splitmind-mcp-server", "python", "/app/mcp-server-redis.py"],
"env": {
"REDIS_URL": "redis://redis:6379"
}
}
}
}
🎯 What Problem Does A2AMCP Solve?
When multiple AI agents work on the same codebase:
- Without A2AMCP: Agents create conflicting code, duplicate efforts, and cause merge conflicts
- With A2AMCP: Agents coordinate, share interfaces, prevent conflicts, and work as a team
Generic Use Cases Beyond SplitMind
A2AMCP can coordinate any multi-agent scenario:
- Microservices: Different agents building separate services
- Full-Stack Apps: Frontend and backend agents collaborating
- Documentation: Multiple agents creating interconnected docs
- Testing: Test writers coordinating with feature developers
- Refactoring: Agents working on different modules simultaneously
🏗️ Architecture
┌─────────────────┐
│ A2AMCP Server │ ← Persistent Redis-backed MCP server
│ (Port 5050) │ handling all agent communication
└────────┬────────┘
│ STDIO Protocol (MCP)
┌────┴────┬─────────┬─────────┐
▼ ▼ ▼ ▼
┌────────┐┌────────┐┌────────┐┌────────┐
│Agent 1 ││Agent 2 ││Agent 3 ││Agent N │
│Auth ││Profile ││API ││Frontend│
└────────┘└────────┘└────────┘└────────┘
🔧 Core Features
1. Real-time Agent Communication
- Direct queries between agents
- Broadcast messaging
- Async message queues
2. File Conflict Prevention
- Automatic file locking
- Conflict detection
- Negotiation strategies
3. Shared Context Management
- Interface/type registry
- API contract sharing
- Dependency tracking
4. Task Transparency
- Todo list management
- Progress visibility
- Completion tracking
- Task completion signaling
5. Multi-Project Support
- Isolated project namespaces
- Redis-backed persistence
- Automatic cleanup
6. Modern MCP Integration
- Uses MCP SDK 1.9.3 with proper decorators
@server.list_tools()and@server.call_tool()patterns- STDIO-based communication protocol
- Full A2AMCP API compliance with 17 tools implemented
📦 Installation Options
Docker Compose (Production)
services:
mcp-server:
build: .
container_name: splitmind-mcp-server
ports:
- "5050:5000" # Changed from 5000 to avoid conflicts
environment:
- REDIS_URL=redis://redis:6379
- LOG_LEVEL=INFO
depends_on:
redis:
condition: service_healthy
restart: unless-stopped
redis:
image: redis:7-alpine
container_name: splitmind-redis
ports:
- "6379:6379"
volumes:
- redis-data:/data
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 10s
timeout: 5s
retries: 5
volumes:
redis-data:
driver: local
Python SDK
pip install a2amcp-sdk
JavaScript/TypeScript SDK (Coming Soon)
npm install @a2amcp/sdk
🚦 Usage Example
Python SDK
from a2amcp import A2AMCPClient, Project, Agent
async def run_agent():
client = A2AMCPClient("localhost:5000")
project = Project(client, "my-app")
async with Agent(project, "001", "feature/auth", "Build authentication") as agent:
# Agent automatically registers and maintains heartbeat
# Coordinate file access
async with agent.files.coordinate("src/models/user.ts") as file:
# File is locked, safe to modify
pass
# File automatically released
# Share interfaces
await project.interfaces.register(
agent.session_name,
"User",
"interface User { id: string; email: string; }"
)
Direct MCP Tool Usage
# Register agent
register_agent("my-project", "task-001", "001", "feature/auth", "Building authentication")
# Query another agent
query_agent("my-project", "task-001", "task-002", "interface", "What's the User schema?")
# Share interface
register_interface("my-project", "task-001", "User", "interface User {...}")
📚 Documentation
- Claude Code Setup Guide
- Installation & Setup
- Full API Reference
- Python SDK Documentation
- Architecture Overview
- SplitMind Integration Guide
🛠️ SDKs and Tools
Available Now
- Python SDK: Full-featured SDK with async support
- Docker Deployment: Production-ready containers
In Development
- JavaScript/TypeScript SDK: For Node.js and browser
- CLI Tools: Command-line interface for monitoring
- Go SDK: High-performance orchestration
- Testing Framework: Mock servers and test utilities
See SDK Development Progress for details.
🤝 Integration with AI Frameworks
A2AMCP is designed to work with:
- SplitMind - Original use case
- Claude Code (via MCP)
- Any MCP-compatible AI agent
- Future: LangChain, CrewAI, AutoGen
🔍 How It Differs from A2A
While inspired by Google's A2A protocol, A2AMCP makes specific design choices for AI code development:
| Feature | Google A2A | A2AMCP |
|---|---|---|
| Protocol | HTTP-based | MCP tools |
| State | Stateless | Redis persistence |
| Focus | Generic tasks | Code development |
| Deployment | Per-agent servers | Single shared server |
🚀 Roadmap
- [x] Core MCP server with Redis
- [x] Modern MCP SDK 1.9.3 integration
- [x] Fixed decorator patterns (
@server.list_tools(),@server.call_tool()) - [x] Python SDK
- [x] Docker deployment
- [x] All 17 A2AMCP API tools implemented and tested
- [x] Health check endpoint for monitoring
- [x] Verification script for testing connectivity
- [ ] JavaScript/TypeScript SDK
- [ ] CLI monitoring tools
- [ ] SplitMind native integration
- [ ] Framework adapters (LangChain, CrewAI)
- [ ] Enterprise features
🛠️ Troubleshooting
Agents can't see mcp__splitmind-a2amcp__ tools
- Restart Claude Desktop - MCP connections are established at startup
- Verify server is running:
docker ps | grep splitmind - Check health endpoint:
curl http://localhost:5050/health - Run verification script:
python verify_mcp.py - Check configuration: Ensure
~/Library/Application Support/Claude/claude_desktop_config.jsoncontains the A2AMCP server configuration
Common Issues
- "Tool 'X' not yet implemented" - Fixed in latest version, pull latest changes
- Connection failed - Ensure Docker is running and ports 5050/6379 are free
- Redis connection errors - Wait for Redis to be ready (takes ~5-10 seconds on startup)
🤝 Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
Development Setup
# Clone repository
git clone https://github.com/webdevtodayjason/A2AMCP
cd A2AMCP
# Install dependencies
pip install -r requirements.txt
# Run tests
pytest
# Start development server
docker-compose -f docker-compose.dev.yml up
📊 Performance
- Handles 100+ concurrent agents
- Sub-second message delivery
- Automatic cleanup of dead agents
- Horizontal scaling ready
🔒 Security
- Project isolation
- Optional authentication (coming soon)
- Encrypted communication (roadmap)
- Audit logging
📄 License
MIT License - see LICENSE file.
🙏 Acknowledgments
- Inspired by Google's A2A Protocol
- Built for SplitMind
- Powered by Model Context Protocol
📞 Support
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Discord: Coming soon
A2AMCP - Turning isolated AI agents into coordinated development teams
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。