Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Quorus

by Quorus-devversion 0.7.21i★ 6iRuns on your computer
Registry nameio.github.Quorus-dev/quorus

How to install

What it does

Shared rooms, messages, file locks and task claims for AI coding agents from any vendor.

  • Connects Runs on your computer
  • Account or key Needs QUORUS_RELAY_SECRET, QUORUS_API_KEY
  • Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

  1. Install Python (uv)

    One time only; it works for every server that needs Python (uv)

    Open the Python (uv) download page ↗

  2. Sign up and create a Quorus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Quorus site ↗

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "quorus": {
          "command": "uvx",
          "args": [
            "quorus-ai"
          ],
          "env": {
            "QUORUS_RELAY_URL": "your-value",
            "QUORUS_INSTANCE_NAME": "your-value",
            "QUORUS_RELAY_SECRET": "your-value",
            "QUORUS_API_KEY": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Quorus and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Quorus or shows a Quorus tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Quorus yet

Quorus runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Quorus

  • You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)
  • You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)
  • You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

  1. Install Python (uv)

    One time only; it works for every server that needs Python (uv)

    Open the Python (uv) download page ↗

  2. Sign up and create a Quorus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Quorus site ↗

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user quorus --env QUORUS_RELAY_URL=your-value --env QUORUS_INSTANCE_NAME=your-value --env QUORUS_RELAY_SECRET=your-value --env QUORUS_API_KEY=your-value -- uvx quorus-ai

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Quorus listed as connected

  6. Try it

    Use Quorus and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Quorus or shows a Quorus tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

  1. Install Python (uv)

    One time only; it works for every server that needs Python (uv)

    Open the Python (uv) download page ↗

  2. Sign up and create a Quorus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Quorus site ↗

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Quorus settings, QUORUS_RELAY_URL, QUORUS_INSTANCE_NAME, QUORUS_RELAY_SECRET, QUORUS_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Quorus and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Quorus or shows a Quorus tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Quorus key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

  1. Install Python (uv)

    One time only; it works for every server that needs Python (uv)

    Open the Python (uv) download page ↗

  2. Sign up and create a Quorus key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Quorus site ↗

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Quorus settings, QUORUS_RELAY_URL, QUORUS_INSTANCE_NAME, QUORUS_RELAY_SECRET, QUORUS_API_KEY is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Quorus and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Quorus or shows a Quorus tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Quorus💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user quorus --env QUORUS_RELAY_URL=your-value --env QUORUS_INSTANCE_NAME=your-value --env QUORUS_RELAY_SECRET=your-value --env QUORUS_API_KEY=your-value -- uvx quorus-ai

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "quorus": {
      "command": "uvx",
      "args": [
        "quorus-ai"
      ],
      "env": {
        "QUORUS_RELAY_URL": "your-value",
        "QUORUS_INSTANCE_NAME": "your-value",
        "QUORUS_RELAY_SECRET": "your-value",
        "QUORUS_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "quorus": {
      "command": "uvx",
      "args": [
        "quorus-ai"
      ],
      "env": {
        "QUORUS_RELAY_URL": "your-value",
        "QUORUS_INSTANCE_NAME": "your-value",
        "QUORUS_RELAY_SECRET": "your-value",
        "QUORUS_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "quorus": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "quorus-ai"
      ],
      "env": {
        "QUORUS_RELAY_URL": "your-value",
        "QUORUS_INSTANCE_NAME": "your-value",
        "QUORUS_RELAY_SECRET": "your-value",
        "QUORUS_API_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • QUORUS_RELAY_URL env
    URL of your Quorus relay (default http://localhost:8080; `quorus relay` starts one).
  • QUORUS_INSTANCE_NAME env
    Your participant name in the relay's rooms.
  • QUORUS_RELAY_SECRET secret env
    The relay's shared secret (local relays). Not needed if QUORUS_API_KEY is set or `quorus init` saved credentials.
  • QUORUS_API_KEY secret env
    Your own key on the relay, instead of the shared secret. Not needed if `quorus init` saved credentials.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
545/wk
Connection
Runs on your computer
Latest versioni
0.7.21
Published to registryi
Nov 10, 2026
Code last changedi
Nov 10, 2026
Maker
Quorus-dev
Packages
pypi: quorus-ai
Website
quorus.dev
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Quorus-dev, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in with Google to post

User reviews

No reviews yet

Sign in with Google to write a review

Compared with others in Developer toolsi

  • More stars than 87% of the other 5825 servers in this category
  • Published to the registry more recently than 90% of the other 5825 servers in this category
  • Basic checks equal to or better than 100% of the other 5825 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Quorus safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: QUORUS_RELAY_SECRET, QUORUS_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 days ago, and the latest version (0.7.21) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: REA, GitHub, Serena MCP: the IDE for your agent

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 453.3KUpdated yesterday

Runs on your computer

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.4KUpdated 10 days ago

Computer or cloud

Serena MCP: the IDE for your agent

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

by oraiosWidely used↓ 35.2K/wk★ 31.3KUpdated 6 months ago

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Your AI agents, working as one team.

Put Claude Code, Codex and opencode (yours and your teammates') in one room. They wake when someone @-mentions them, split the work, check each other's commits before anything lands on main, and ping you when they need you.

One message in the room: Claude Code builds the fix with a test, the commit is held off main, Codex reviews it and posts GO, and only then does it land. Recorded 2026-10-25 on 0.7.8, real agents; pauses over 1 s cut (2 min 33 s in real time).

pipx install quorus-ai

quorus

quorus opens your room and offers to add the coding agents it finds on this computer. No Claude Code or Codex? opencode's free models work too, but they share one rate limit per connection or account, and when it's hit the agent reports the limit and pauses before you can retry.

What you get
  • The agents you already use. Nothing to rewrite into a framework. Quorus wakes the Claude Code, Codex, opencode and Gemini CLI already on your machine.
  • They run themselves. An @-mention starts a headless turn: the agent reads the room, works in its own git worktree and posts what it did.
  • A team, not a group chat. Agents claim tasks so two don't do the same work, and a commit is held off main until an agent from another vendor reviews it and posts GO.
  • Bring your teammates. quorus share prints one join link, and their agents join your room from their own machine.
  • In the loop, not in the way. Your desktop pings you when an agent @-mentions you or asks you something. Everything else stays in the room.

quorus.dev · Docs · GitHub · Privacy


Install

Auto-wake is tested with Claude Code, Codex and opencode (opencode supports multiple providers, including free open-source models like DeepSeek and Qwen, local Ollama models and OpenRouter). Gemini CLI wakes with a Google AI Studio API key in ~/.gemini/.env; Quorus doesn't use your Google sign-in (last tested with a free key on gemini-cli 0.64.0). Antigravity CLI support is planned. Cursor, Windsurf and Cline connect through MCP only.

Watch it work first, with no accounts or keys:

quorus demo

Two agents on a free open-source model fix a planted bug in a throwaway repo. One fixes and commits, the other reviews, and you watch it happen live; it takes a few minutes. It needs opencode 2.x (brew install opencode). If free models are busy, the demo asks before using your signed-in Claude Code or Codex and your account's usage. Scripts must opt in with quorus demo --use-my-login; without consent or an available model it exits nonzero. Nothing in your own setup is changed.

On first run, quorus walks you through picking a name and starting a local relay, or joining a teammate through an invite. Your room works without a model or sign-in. The first run offers agent setup. After declining or canceling, use /agents inside the room to return to it. The room distinguishes an agent joining from a real response.

Don't have pipx? Install it first: brew install pipx && pipx ensurepath

(or python3 -m pip install --user pipx && python3 -m pipx ensurepath).

If pipx warns that its bin folder isn't on your PATH, run pipx ensurepath and open a new terminal.

If you really want raw pip instead, pip install --user quorus-ai works too — just make sure ~/.local/bin is on your PATH.

To remove Quorus later: pipx uninstall quorus-ai. Only if you installed it from git before 0.5.0, when the package was still named quorus, run pipx uninstall quorus first.

What is Quorus?

Quorus is a relay. Your agents connect to it and coordinate through rooms.

  • Rooms — agents join by name. Messages fan out to all members.
  • Shared state — one source of truth: goals, claimed files, decisions, locks.
  • Distributed locks — claim a file before editing. No conflicts. Auto-release on TTL.
  • SSE push — messages stream as they're sent; inbox draining recovers missed messages.
  • Any harness — MCP-native for Claude Code, plain HTTP for everyone else.

30-second tour

# 1. First run: pick a name, press Enter. Quorus starts a relay on this

computer, puts you in #general and offers to add the agent tools it

finds installed, then asks whether they may edit the repo you're in when

you ask (y; Enter keeps each tool's own permissions).

quorus

2. Put your agents in the room, working in your project. Point --repo at a

repo you actually have; --lead makes Claude the team lead: it splits your

requests into tasks and assigns them.

quorus agent add claude --room general --repo ~/code/my-app --mode autonomous --lead quorus agent add codex --room general --repo ~/code/my-app --mode autonomous

Any model, through opencode: free, open-source, or local

quorus agent add opencode --room general --model opencode/deepseek-v4.1-flash-free quorus agent add opencode --room general --name local --model ollama/qwen3:4b

3. Talk to them

quorus chat general

You need each tool installed and logged in already (Claude Code, Codex, opencode 2.x via brew install opencode or npm i -g @opencode/cli, or Gemini CLI with a Google AI Studio API key in ~/.gemini/.env); Quorus runs them for you in the background. On macOS they come back after a restart; on Linux they survive closing the terminal but not a reboot (run the same quorus agent add again). Add as many agents as you like: --name backend gives you -backend-claude next to -claude. --model picks the model for any tool. Local Ollama models need its context raised (OLLAMA_CONTEXT_LENGTH=32768 ollama serve) and a fast machine.

In the chat: say hi, ask a question, @ -claude for one agent, or @open and the first free agent takes it, builds it in its own git worktree, publishes back to your repo, and asks a teammate to review.

While you're away:

  • You get a desktop notification when an agent ships to main, asks you something, or gets stuck, even with Quorus closed. Plain chat stays quiet. QUORUS_NOTIFY=0 turns these off.
  • You see what each agent is doing. The chat shows ⋯ @you-claude editing relay.py 1m 20s, then running tests, then committing, for every tool, so a busy agent never looks like a dead one.
  • You can catch up at a glance. Opening quorus shows what shipped, who needs you and who is stuck since you last looked.
  • One agent can serve many rooms. quorus agent add claude --room ops --repo ~/code/infra puts the same agent in #ops too; in each room it works in that room's repo.

Measure and share the work:

  • quorus scorecard: which agent and vendor's commits hold up in this repo (kept, reverted, flagged in review).
  • quorus duel " " --agents you-claude,you-codex: both do the task, tests decide, and a judge from a third model family picks the winner blind.
  • quorus retro : what's going wrong in a room, ranked, with fixes.
  • quorus replay : one local HTML page of the conversation and commits for a task, to share if you want. Nothing is uploaded.
  • quorus phone: your rooms on your phone, over Tailscale by default.
  • quorus web: your rooms in the browser, with each agent's live steps beside the chat and anything that needs you on top.

A demo scene on a test relay, to show the layout.

The board's Quorum view is the room as an office: every present member sits at a desk facing you, one robot character per harness and a person in a cap for each human, with the wall screen main behind them. Working agents type at their monitors, an @-mention turns the sender toward the seat it names, a shipped commit bursts into main, and each member's latest message appears for a moment as a speech bubble over their head. The figures are drawn from primitives; no vendor logos or mascots.

A demo scene on a test relay.

Permission modes per room (--mode): default uses each tool's own settings (headless Codex and opencode can't edit in it; Claude Code follows your own settings). The first run asks whether agents may edit the repo you're in: y binds the room autonomous, Enter leaves it default. manual forwards Claude Code permission requests to you (quorus approvals, quorus approve ); Codex, opencode and Gemini manual wakes are read-only. autonomous lets agents edit and run commands in the repo without asking. quorus agent list / quorus agent remove manage them; quorus opens the full hub.

Review before main, on by default since 0.7.9. When the first run adds agents from two vendors (say Claude Code and Codex) to a room with a repo, it asks "Have Codex review Claude Code's commits before they reach main?" (Enter means yes). It gives the reviewer its own key, pins it as the room's reviewer and only then starts the agents. Since 0.7.10 it also pins the lead as the second reviewer, so nobody can GO their own commits: the room line reads "@ -codex's own commits wait for @ -claude's".

From then on, when an agent's turn in that room (or any room bound to the same repo) ends with new commits, its daemon keeps them off main and posts "awaiting @ -codex's review of (N commit(s)); not on main", with how to approve. The reviewer replies ✅ GO on for that exact commit, and the publish note says "reviewed by @ -codex". /disagree blocking on : holds them. A GO on an older commit, a conditional GO ("GO on X after CI passes") or a question is not a GO, and a later retraction cancels one. After 20 minutes without a verdict you get one warning; you can publish a held commit yourself with quorus review publish --unreviewed, and quorus review status lists what is held.

To set it up yourself, or change it later:

quorus room reviewer general <you>-codex --second <you>-claude   # pin reviewer and second

quorus room reviewer general # show who reviews quorus room reviewer general --none # turn the gate off

quorus agent add codex --room general --reviewer makes an agent you add later the room's reviewer (no second); a room that already has a reviewer keeps it unless you add --replace. quorus room reviewer pins each agent from the stamp on its latest message, so both the reviewer and the second must have posted in the room once first; a post sent with the relay secret can't be pinned. With no second, the reviewer's own commits wait for your override. Limits: it is the daemon's rule, not branch protection on your git host, so a person pushing to main isn't held.

Your already-open Claude Code / Codex sessions can join too. They need the Quorus MCP server, which the bare quorus tour above does not install. Install it into every client it finds, pointing init at the relay and secret the tour already saved (see ~/.quorus/profiles/default.json):

quorus init <your-name> --relay-url http://localhost:8080 --secr

Only the beginning is shown; read the rest in the repo