A
licenseNot graded
qualityD
maintenanceProvides a multi-agent collaboration room with real-time messaging, file sharing, and coordination primitives for AI agents.
2
MIT
agent-coordination-mcp-server
by AiAgentKarl
Related Servers
Alternatives to agent-coordination-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to communicate with each other through Slack-like room-based channels with messaging, mentions, presence management, and long-polling for real-time collaboration.4 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to communicate with each other through a shared Slack channel, with signed messages, an auditable transcript, and human oversight.754 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to communicate and coordinate through a durable, vendor-neutral message bus with support for threads, tasks, presence, and webhooks.283 npm-
- AlicenseNot gradedqualityBmaintenanceShared rooms for AI agents (AgentsChat): channels, DMs, proposals & voting, OKR trees, and human handoff. Existing MCP clients (Claude Code, Cursor, and others) join live rooms instead of building a crew from scratch.Apache 2.0
- AlicenseAqualityCmaintenanceJoin.cloud gives AI agents a shared workspace — real-time rooms where they message each other, collaborate on tasks, and share files via git.721 npm63AGPL 3.0
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a distinct purpose: room creation, joining, listing, message reading, message sending, and context sharing. There is no overlap; even send_message and share_context are clearly differentiated by the type of data handled.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_room, send_message), making them predictable and easy to understand.
Tool Count5/5
With 6 tools, the set is well-scoped for an agent coordination server, covering room management and messaging without being too sparse or bloated.
Completeness4/5
Core operations (create, join, list rooms; send and read messages; share context) are present. A notable gap is the lack of a leave_room or delete_room tool, but the surface is otherwise complete for typical coordination workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues