Coordinates multiple AI agents working on the same codebase through Redis-backed infrastructure, preventing conflicts with file locking and enabling real-time communication between agents.

Coordinates multiple AI agents working on shared codebases through Redis-backed infrastructure that provides real-time messaging, file locking to prevent simultaneous edits, interface sharing for type definitions, and distributed task management across parallel development sessions.

19286 views3Local (stdio)

What it does

  • Lock files to prevent simultaneous edits by multiple agents
  • Send real-time messages between AI agents
  • Share interface definitions across agent sessions
  • Manage distributed tasks across parallel development workflows
  • Track agent activities and coordination status
  • Synchronize codebase changes between agents

Best for

AI development teams with multiple agents working on shared codeParallel AI-powered development workflowsMulti-agent coding systems requiring coordination
Redis-powered real-time coordination17 coordination toolsDocker-ready deployment

About A2AMCP

A2AMCP is a community-built MCP server published by webdevtodayjason that provides AI assistants with tools and capabilities via the Model Context Protocol. A2AMCP synchronizes multiple AI agents on shared codebases with Redis-powered messaging, file locking, interface sharing It is categorized under ai ml, developer tools.

How to install

You can install A2AMCP in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

A2AMCP is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

A2AMCP - Agent-to-Agent Model Context Protocol

License: MIT Docker Redis Status

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

🛠️ 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:

FeatureGoogle A2AA2AMCP
ProtocolHTTP-basedMCP tools
StateStatelessRedis persistence
FocusGeneric tasksCode development
DeploymentPer-agent serversSingle shared server

🚀 Roadmap

  • Core MCP server with Redis
  • Modern MCP SDK 1.9.3 integration
  • Fixed decorator patterns (@server.list_tools(), @server.call_tool())
  • Python SDK
  • Docker deployment
  • All 17 A2AMCP API tools implemented and tested
  • Health check endpoint for monitoring
  • 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

  1. Restart Claude Desktop - MCP connections are established at startup
  2. Verify server is running: docker ps | grep splitmind
  3. Check health endpoint: curl http://localhost:5050/health
  4. Run verification script: python verify_mcp.py
  5. Check configuration: Ensure ~/Library/Application Support/Claude/claude_desktop_config.json contains 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

📞 Support


README truncated. View full README on GitHub.

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

6
cli-builder

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

2
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

0
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

0
ydc-ai-sdk-integration

Integrate Vercel AI SDK applications with You.com tools (web search, AI agent, content extraction). Use when developer mentions AI SDK, Vercel AI SDK, generateText, streamText, or You.com integration with AI SDK.

0
mcp-developer

Use when building MCP servers or clients that connect AI systems with external tools and data sources. Invoke for MCP protocol compliance, TypeScript/Python SDKs, resource providers, tool functions.

0