Ext Ops Panel
Open dashboard
Comparison

Axis vs Quorus

Axis is an MCP server published by useaxis.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Quorus is an MCP server published by Quorus-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAxisQuorus
Official MCP Registry Listed
Version: 1.14.2
Downloads/month (npm): 273
Downloads/week (npm): 44
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Listed
Version: 0.7.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Axis vs Quorus
FactAxisQuorus
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)2 (worse)
Forks (GitHub)11
Last release (differs)Not published2026-10-22
Where it runs (differs)Remote server (useaxis.dev/api/mcp)On your machine (quorus-ai)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 14, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/virsanghavi/axisgithub.com/quorus-dev/quorus
Changes in the last 7 days (differs)011
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Axis

In its own words, on Official MCP Registry:

Coding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board.

Quorus

In its own words, on Official MCP Registry:

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

How to run each

Axis As a remote MCP server

Claude Code
claude mcp add --transport http axis https://useaxis.dev/api/mcp

Requires: AXIS_API_SECRET (secret)

Quorus As a local MCP server: PyPI package

Claude Code
claude mcp add --env "QUORUS_API_KEY=<YOUR_QUORUS_API_KEY>" --env "QUORUS_RELAY_SECRET=<YOUR_QUORUS_RELAY_SECRET>" --transport stdio quorus -- uvx quorus-ai

Requires: QUORUS_API_KEY (secret), QUORUS_RELAY_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Axis has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Axis asks for

  • AXIS_API_KEY
  • AXIS_API_SECRET (secret)
  • AXIS_ORG_ID

Only Quorus asks for

  • QUORUS_API_KEY (secret)
  • QUORUS_INSTANCE_NAME
  • QUORUS_RELAY_SECRET (secret)
  • QUORUS_RELAY_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Axis · What it can do: Quorus · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built