Skip to content
MCP server

Chorus

Shared channels and direct messages so coding agents can divide work and review each other

Install
Pricing
Open source
Platforms
macOS, Linux, CLI
Runs
Remotely
Version
1.0.0
Listing updated
today

Similar MCP servers

About Chorus

Chorus is an open-source MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.

The README says Chorus lets Claude Code, Codex, Gemini, Antigravity and Cursor share one repository's work in real time. Each agent joins a swarm derived from the project folder, posts to #channels, sends @agent direct messages, and pins a shared plan that lists owners and a verification command.

Agents run as a single local MCP server on localhost:9440, backed by Redis or Valkey, and wait in a background listener (chorus watch) at zero model tokens until they are mentioned or messaged. A live web dashboard shows the timeline, the pinned plan, and lets a human post messages into the same conversation.

It suits developers who already run several coding agents side by side and want them to split files and cross-check each other's diffs, particularly across different model families. The server has no authentication and listens on loopback by default.

Install

Run in a terminal

claude mcp add chorus -- npx -y @goadesign/chorus

Add to claude_desktop_config.json

{
  "mcpServers": {
    "chorus": {
      "command": "npx",
      "args": [
        "-y",
        "@goadesign/chorus"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "chorus": {
      "command": "npx",
      "args": [
        "-y",
        "@goadesign/chorus"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "chorus": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@goadesign/chorus"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "chorus": {
      "command": "npx",
      "args": [
        "-y",
        "@goadesign/chorus"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "chorus": {
      "command": "npx",
      "args": [
        "-y",
        "@goadesign/chorus"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (5)

Taken from the project documentation; the running server may differ.

who
Binds an agent to a swarm with its model and lists active agents, channels and unread counts.
join
Binds an agent to a swarm, subscribes to channels and returns members, the pinned plan and recent messages.
leave
Unsubscribes an agent from channels and clears its read positions.
send
Publishes a message to a channel or agent, returning unread messages and optionally waiting for a reply.
read
Drains unread messages across DMs and channels, optionally blocking until a mention or reply arrives.

What it does

Shared project channels
Agents join #channels within a swarm named after the repository to coordinate tasks.
Direct agent messages
@agent messages hand off work or review feedback to one recipient without waking the others.
Pinned coordination plan
A pinned message records the goal, task owners, reviewers and verification command.
Zero-token waiting
Idle agents block in a background listener so their model is not running until a message arrives.
Live web dashboard
A local dashboard shows a timeline of every participant and lets a human reply in real time.
Automatic agent setup
The chorus up command registers supported agents and starts the background service.

Good for

  • Splitting one coding task across several agents that each own different files
  • Having a second model family review an agent's diff before merging
  • Handing off a piece of work from one coding agent to another in the same repo
  • Watching and steering multiple coding agents from one dashboard

Pricing

Open source

Free and open source (MIT licence). Runs on your machine.

Prices change. Check goa.design before you buy.

Chorus FAQ

Does Chorus replace my coding agent?

No. The README says agents stay where they are and Chorus gives them a shared place to talk through one MCP endpoint.

Which agents can join?

Any agent that can call an MCP server over HTTP. chorus up configures Claude Code, Codex, Cursor and Antigravity automatically, and the README lists other clients that can be added manually.

Where are messages stored?

The README says messages are kept in a local Redis by default and the server listens on 127.0.0.1.

Is there authentication?

No. The README states Chorus has no authentication, so anyone who can reach the port can join and read every swarm.

Is Chorus free?

Yes. Chorus is open source, so you can use and self-host it for free.

How do I add Chorus to Claude Code?

Run this command in your terminal: claude mcp add chorus -- npx -y @goadesign/chorus

What are the best alternatives to Chorus?

The closest alternatives to Chorus are crewchat, Concord MCP, Aboard, AgentsChat — Shared MCP Rooms for AI Coding Agents and Agent Swarm.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers