SplitMind MCP Agent Communication Server (Redis Edition)
@webdevtodayjason
About SplitMind MCP Agent Communication Server (Redis Edition)
A2AMCP is a Agent2Agent MCP communication Server taking the concept from Google's Agent2Agent Protocol (A2A)
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"A2AMCP": {
"command": "docker",
"args": [
"exec",
"-it",
"splitmind-redis",
"redis-cli"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is SplitMind MCP Agent Communication Server (Redis Edition)?
A persistent, multi-project MCP server that enables real-time communication between AI agents working on parallel tasks in SplitMind. Built with Docker and Redis for reliability and scalability.
How to use SplitMind MCP Agent Communication Server (Redis Edition)?
Clone the repository, make entrypoint.sh executable, and start services with docker-compose up -d. Each Claude Code agent must be configured with the JSON MCP server configuration pointing to the Docker container. Agents then use provided tools like register_agent, heartbeat, add_todo, and query_agent to coordinate.
Key features of SplitMind MCP Agent Communication Server (Redis Edition)
- Multi-project isolated namespaces for different projects
- Persistent state via Redis that survives restarts and crashes
- Per-agent todo list management with priority and status
- Automatic dead agent detection and cleanup via heartbeats
- Docker deployment for easy setup and scalability
- Optional Redis Commander web UI for real-time monitoring
Use cases of SplitMind MCP Agent Communication Server (Redis Edition)
- Parallel AI agents working on separate tasks in the same project
- File coordination with locks to prevent conflicts
- Inter-agent queries and broadcasts for status and help
- Sharing TypeScript interfaces and type definitions across agents
- Tracking progress and task breakdown across all agents
FAQ from SplitMind MCP Agent Communication Server (Redis Edition)
What are the runtime dependencies?
Docker and Docker Compose are required. The server uses a Redis container; optional Redis Commander container for monitoring.
How does dead agent cleanup work?
Agents must call heartbeat() every 30–60 seconds. If a heartbeat is missed, the agent is automatically cleaned up.
How can I monitor the system?
Use Redis Commander at http://localhost:8081 (with debug profile), Docker logs, or direct Redis CLI via docker exec.
How can I secure the deployment in production?
Remove Redis port exposure, add a Redis password via REDIS_URL, and set resource limits on containers.
What data is stored per project?
Each project has a Redis namespace containing: agents hash, heartbeat timestamps, file locks, shared interfaces, agent todo lists, message queues, and a list of recent file changes.
Frequently asked questions
What are the runtime dependencies?
Docker and Docker Compose are required. The server uses a Redis container; optional Redis Commander container for monitoring.
How does dead agent cleanup work?
Agents must call `heartbeat()` every 30–60 seconds. If a heartbeat is missed, the agent is automatically cleaned up.
How can I monitor the system?
Use Redis Commander at `http://localhost:8081` (with debug profile), Docker logs, or direct Redis CLI via `docker exec`.
How can I secure the deployment in production?
Remove Redis port exposure, add a Redis password via `REDIS_URL`, and set resource limits on containers.
What data is stored per project?
Each project has a Redis namespace containing: agents hash, heartbeat timestamps, file locks, shared interfaces, agent todo lists, message queues, and a list of recent file changes.
Basic information
More AI & Agents MCP servers
欢迎来到 智言平台
Shy2593666979AgentChat 是一个基于 LLM 的智能体交流平台,内置默认 Agent 并支持用户自定义 Agent。通过多轮对话和任务协作,Agent 可以理解并协助完成复杂任务。项目集成 LangChain、Function Call、MCP 协议、RAG、Memory、HITL、Skill、Milvus 和 ElasticSearch 等技术,实现高效的知识检索与工具调用,使用 FastAPI 构建高性能后端服务。
Hass-MCP
voskaControl and query Home Assistant from Claude and other LLMs — a Model Context Protocol (MCP) server.
MCP Client for Ollama (ollmcp)
joniglHarness the power of local LLMs with this TUI MCP Client for Ollama. Featuring all core MCP primitives (tools, prompts, resources), agent mode, multi-server, model switching, streaming responses, human-in-the-loop, thinking mode, model params config, system prompts, and saved pre
Model Context Protocol Server for Home Assistant
tevonsbA MCP server for Home Assistant
MCP Claude Code
SDGLBLMCP implementation of Claude Code capabilities and more
Comments