mcp-agent-collaboration
Related Servers
Alternatives to mcp-agent-collaboration
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables AI agents and teams to coordinate through shared inboxes, threaded conversations, attachments, expiring file reservations, prompts, and live notifications, while replaying missed events after restarts.443 npm2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Agent Room, enabling AI agents to join shared meeting rooms and collaborate with humans via tools like room_listen and room_task_*.1MIT
- AlicenseNot gradedqualityFmaintenanceA local MCP server that provides shared, real-time context across multiple AI agents via WebSocket and MCP resource notifications, enabling collaborative workspaces, memory, tasks, and messaging.10 npm2MIT
- AlicenseNot gradedqualityCmaintenanceA production-ready MCP server that enables multiple AI agents to collaborate through a shared, concurrency-safe memory space. It supports advanced search, full CRUD operations, and automatic backups to facilitate asynchronous communication between agents.MIT
- AlicenseAqualityDmaintenanceMCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.835 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.107 npm9MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: topic lifecycle (create, join, leave), messaging (send, read, check_in), and listing (topics, members). check_in is a convenience combination but its description clarifies its dual role.
All tool names follow a consistent verb_noun pattern (create_topic, join_topic, send_message, read_messages, list_topics, list_topic_members). Minor phrasal verb 'check_in' still fits the style.
Eight tools cover the domain of topic-based collaboration without redundancy or bloat. Each tool serves a distinct function and the count is well within the ideal range.
The surface covers topic creation, joining/leaving, messaging, and listing topics/members. A delete_topic operation is missing but might be intentionally omitted for ephemeral in-memory topics, so minor gap only.