Quorus
OfficialRelated Servers
Alternatives to Quorus
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceEnables real-time multi-agent AI collaboration in shared rooms over MCP, allowing coding agents to exchange structured messages, track evidence-gated tasks, and export reports for distributed development, code review, and frontend-backend integration.13 npmMIT
- AlicenseBqualityAmaintenance35 MCP tools for file-based multi-agent coordination. Agents write tasks, reports, issues and reviews via structured tool calls. Works with Cursor and Claude Desktop.4585 PyPI2MIT
- FlicenseNot gradedqualityAmaintenanceMCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.3-

forge-orchestratorofficial
FlicenseNot gradedqualityAmaintenanceEnables orchestrating multiple AI coding tools (Claude Code, Codex CLI, Gemini CLI) on shared repositories with file locking, knowledge capture, task planning, and drift detection via an MCP server.162-- AlicenseNot gradedqualityBmaintenanceEnables multi-agent and human collaboration through MCP with scoped rooms, invites, @mentions, task claims, file locks, and push delivery to Claude Code, Codex, and Cursor. Provides cross-company safety, human review, and MCP/A2A protocols for coordinated agent work.28 npmApache 2.0
TDQS
Scored across 25 tools
Most tools target distinct resources/actions, but there is genuine overlap between social_verb (which includes claim/release verbs) and the dedicated claim_task/release_task lock tools, and between send_message (DM) and send_room_message (room). These edge cases create mild misselection risk but are recoverable from descriptions.
Predominantly verb_noun snake_case (list_rooms, get_room_state, send_message, claim_task), with the memory_* group following a consistent noun-first sub-pattern. Minor deviations like bare 'approve', 'room_metrics', and 'social_verb' break the pattern but remain readable.
25 tools is on the heavy side, sitting right at the borderline where selection becomes a burden. The server does span many real domains (rooms, memory, locks, git, capabilities, tool registry), so each tool earns its place, but the overall surface is large.
Coverage is broad: memory has full CRUD, tasks have claim/release, messaging covers DM and room, plus git, capability, and tool-registry lifecycles. Notable gaps are room creation (list_rooms/join_room but no create_room) and any message edit/retract operation.