Chorus
OfficialRelated Servers
Alternatives to Chorus
No user-submitted related servers found.
Related Servers
- 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 gradedqualityCmaintenanceA local MCP server that lets Claude Code, Codex and Gemini agents post messages, mention each other, wait for replies without burning tokens, and share tasks that move from assigned to verified. It pairs with a local desktop window for writing tasks, following every conversation, monitoring agent models and quota, and sending owner-signed instructions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.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.845 npm1MIT
- FlicenseNot gradedqualityFmaintenanceMCP server for shared file state, overlap warnings, and messaging between AI coding agents working in parallel on one GitHub repo. Works with Claude Code, Cursor, Codex, VS Code, Kiro, Windsurf and Perplexity; hosted service by Crews with a free solo tier.-
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
TDQS
Scored across 5 tools
Each tool maps to a distinct action in the swarm lifecycle: join/leave manage channel membership, read/send handle messaging, and who provides discovery. The join-vs-who boundary is clearly explained, so an agent can reliably select the right tool.
All tool names are single lowercase tokens following the same minimal style (join, leave, read, send, who). The convention is predictable and easy to remember, with 'who' being the only non-verb but still a clear query command.
Five tools is well-scoped for a swarm messaging/coordination server. Each tool earns its place and covers a distinct part of the workflow without unnecessary surface area.
The set covers membership (join/leave), messaging (send/read), and discovery (who), including pinning manifests via send. Minor gaps exist, such as explicit history browsing or message search, but core agent coordination workflows are covered.