ai-mldeveloper-tools

A2AMCP

webdevtodayjason

by webdevtodayjason

A2AMCP synchronizes multiple AI agents on shared codebases with Redis-powered messaging, file locking, interface sharing

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.

github stars

19

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Redis-powered real-time coordination17 coordination toolsDocker-ready deployment

best for

  • / AI development teams with multiple agents working on shared code
  • / Parallel AI-powered development workflows
  • / Multi-agent coding systems requiring coordination

capabilities

  • / 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

what it does

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.

about

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

MIT

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

readme

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


FAQ

What is the A2AMCP MCP server?
A2AMCP is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for A2AMCP?
This profile displays 36 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.536 reviews
  • Ganesh Mohane· Dec 12, 2024

    We evaluated A2AMCP against two servers with overlapping tools; this profile had the clearer scope statement.

  • Kiara Malhotra· Dec 4, 2024

    A2AMCP has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Daniel Bansal· Nov 23, 2024

    A2AMCP is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Harper Harris· Nov 11, 2024

    A2AMCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Xiao Wang· Oct 14, 2024

    We wired A2AMCP into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Kaira Anderson· Oct 2, 2024

    Useful MCP listing: A2AMCP is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Rahul Santra· Sep 9, 2024

    Useful MCP listing: A2AMCP is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Sophia Sanchez· Sep 5, 2024

    We evaluated A2AMCP against two servers with overlapping tools; this profile had the clearer scope statement.

  • Sophia Agarwal· Sep 5, 2024

    Useful MCP listing: A2AMCP is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Pratham Ware· Aug 28, 2024

    A2AMCP reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

showing 1-10 of 36

1 / 4