How-to guides

Use agent access

Let a coding agent read your Company through Quorum's MCP server, and ask it for advice. The agent reads; you play.

Use this guide when you want a coding agent, such as Claude Code or Codex, to read your Company and tell you what to fix.

Quorum serves a read-only MCP endpoint at https://playquorum.dev/mcp. Your browser uploads a snapshot of the open Company every few seconds while Agent access is on, and the endpoint answers from the last upload. The agent can read the Board, the incidents, and the Inbox, but it cannot place a Node, click a button, or change a setting.

Before you start#

  • An agent that supports remote MCP servers over Streamable HTTP.

  • A Company open in playquorum.dev.

Add the endpoint to your agent#

  1. Add the server. For Claude Code, run:

    claude mcp add --transport http quorum https://playquorum.dev/mcp

    For Codex, add this to ~/.codex/config.toml:

    [mcp_servers.quorum]
    url = "https://playquorum.dev/mcp"
  2. Start the agent. There is no install step, no local port, and no key.

Turn on Agent access#

  1. Open the game menu with Esc and select Settings.

  2. Turn on Agent access. It is off by default, and the game remembers your choice.

  3. Copy the Agent room id under the switch.

The id is a name for the snapshot, not a password. The write key stays in your browser, so another person with the id can read the Company but cannot replace what the agent sees. Turning Agent access off deletes the snapshot.

Ask the agent#

  1. Include the id in your question, for example: "Read agent room abcDEFghiJKLmnoPQRstuv and tell me what to fix first."

  2. Check that the agent calls get_status, then get_company. The status says how old the snapshot is. If the answer names your Cash, users, and Era, the connection works.

The agent has eight tools, and all of them only read:

ToolWhat it returns
get_statusWhen the snapshot last synced, the mode, and how much it holds. Call it first.
get_companyCash, users, Apdex, the Era, latency percentiles, revenue, Burn, the bottleneck, and your Research. Start here.
get_designEvery Node with its inbound and outbound Links and their rates, live load, drops, and each kind's health.
get_incidentsThe running incident, the alert rules and alarms, and recent postmortems.
get_inboxYour mail, with the choices each message offers. The agent can read the choices, not take them.
get_historyRecent samples of users, revenue, Burn, latency, p99, Apdex, and errors, to see trends.
explain_nodeWhy one Node is busy: its Load change, the traffic behind it, and the research that reveals it.
get_gameThe whole saved Game as JSON. It is large, so the agent should prefer the others.

The server also offers the wiki as resources. quorum://wiki/index lists them: how requests flow, latency, errors and retries, incidents, money, and a page for each Component. An agent that reads a page can explain your Design with the game's own rules instead of guessing. The design document, the patterns, and the reference pages stay on the website.

Every tool takes the room id as its room argument. The agent reads the last upload, so pause the game (Space) if you want its answer to match what you see. When you close the tab, the last snapshot stays for 24 hours.

Apply the advice yourself#

  1. Read what the agent suggests.

  2. Check the claim on the board before you act. For example, select the Node it names and read its Load row, which Find the bottleneck covers in full.

  3. Make the change yourself, then ask the agent to read the Company again.

When it does not answer#

Message from the agentFix
"Pass the agent room id shown in Quorum Settings…"Copy the id under Agent access and include it in the question.
"This Room has no snapshot yet…"Open the Company and turn on Agent access.
"A Challenge is open."Challenges are scored, so no agent can read them. Leave the Challenge first.
The figures are older than the gameThe tab is closed or asleep. Bring it to the front; the last snapshot stays until a new one.
"No Room is open…"Open a Company.

When the agent cannot connect#

Open Settings and select Copy state as JSON. Paste the result into your agent. The JSON holds the same views that the tools return, and it answers nothing while a Challenge is open either. Copy it again each time the game changes.