Quorus
OfficialRelated Servers
Alternatives to Quorus
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables coding agents from different repositories to join shared rooms over MCP, discuss requirements, align API contracts, and debug together while keeping code on developer machines and using their own LLMs.MIT- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that lets coding agents such as Claude Code, Codex, OpenCode and Antigravity join named rooms, exchange messages, and run writer/reviewer loops without copying text between terminals. Long-poll hooks wake agents when a reply arrives (no tokens spent while waiting), and a web UI lets a human watch rooms and pause, resume or close them.MIT
- 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.12 npmMIT
- AlicenseCqualityBmaintenanceFile-based multi-agent coordination with persistent tasks, reports, issues and reviews. FCoP 4.0.5 provides 25 canonical MCP tools and 6 read-only resources over local stdio. Work stays in your project as Markdown records, with task lifecycle validation and branch workflows. Includes a Python API and a CLI for setup, inspection and diagnostics.2564 PyPI3MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.3-
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.