Open menu
Codon MCP

Your coding agents need one queue.

Codon gives Claude Code, Codex, Cursor and your other MCP clients one shared task queue — the same one CodonTerminal runs. Queue it anywhere. Claim it once. Review it before it's done.

Install freeGet Gattaca Plus

Node.js 20+ · local-first · 9 tools free · no account required

codon · status

CodonTerminal is running · Queue running

Claude Code

claude
Signed in

Codex

codex
Signed in

Gemini CLI

gemini
Signed in

Queue

2 queued · 3 running · 1 waiting for review

Illustration with sample data

01

Queue

Any agent adds a task to the project's queue, in plain English.

02

Claim

An agent takes a task and gets the project brief with it. No collisions.

03

Run

Or CodonTerminal's queue runs it in a worktree, on a subscription with room.

04

Review

Finished work waits in Review with a summary and a diff.

Install

Connect your first agent.

Codon is a stdio MCP server. Your client starts it when a chat needs it; there is no daemon to manage. Have CodonTerminal? Settings → Connect tools gives you these commands using the copy bundled with the app, so there's no npm step.

Codex · Windows

Add an MCP server

Tested
  1. 1. Open Settings → MCP servers → Add server.
  2. 2. Name it codon.
  3. 3. Enter the command and arguments below.
  4. 4. Restart Codex, open a new chat, then enter /mcp.
Command:   cmd
Arguments: /c npx -y codon-mcp

Verified with GPT-5.6 Sol. If another model does not expose local MCP tools, switch to a Codex model and start a new chat.

Claude Code

Add from your terminal

Run this in the project you want Codon to coordinate:

claude mcp add codon -- cmd /c npx -y codon-mcp

macOS or Linux:

claude mcp add codon -- npx -y codon-mcp

Use --scope user before -- to make it available across projects.

Any MCP client

Use standard JSON configuration

Save this in the client's local MCP configuration. On macOS or Linux, use npx directly.

{
  "mcpServers": {
    "codon": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "codon-mcp"]
    }
  }
}

Tools

Nine tools free. Planning with Plus.

Codon Core

9 tools, free

No account
  • codon_status

    See which coding CLIs are signed in, which are resting after a usage limit, and whether the queue is running or paused.

  • codon_tasks

    List the project's queue: Queued, Running, Review, Done.

  • codon_task_add

    Queue a task, optionally pinned to a tool or model.

  • codon_task_update

    Edit a task, add a note, or change its status.

  • codon_task_claim

    Take a task to do in this chat. The brief comes with it.

  • codon_task_complete

    Report it ready for review, done, failed, or handed back.

  • codon_brief

    Read or replace the one context file every task sees.

  • codon_run

    Start a task on CodonTerminal's swarm, in its own git worktree.

  • codon_usage

    Subscription usage from the CLIs' own local logs, plus today's API spend.

Gattaca Plus

Plan from a goal

$15/month
  • codon_plan

    Turn one goal into a queue of ready-to-run tasks. Runs through CodonTerminal.

codon_plan needs CodonTerminal open, with your Gattaca key in Settings → License. In the app, Plus also adds Second opinion: a model from a different vendor reviews a change before you merge it.

Get Gattaca Plus

Coming from codon-mcp 0.3? 2.0 replaces the board, mission and reviewer tools with the queue above; CodonTerminal 2.0 imports your old board the first time it opens a project. Still on CodonTerminal 0.1.x? Pin the old server with npx -y codon-mcp@0.3.

Two ways to run

Works on its own. Does more with the app open.

With CodonTerminal running, every call goes through its engine and the queue updates on screen at once. With the app closed, the task tools read and write the project's .codon/tasks.json directly, with the same code the app uses.

ToolApp closedApp open

Queue, claim, complete, update

YesYes

Read or replace the brief

YesYes

Status and usage

YesYes, plus live routes

codon_run — start it on the swarm

—Yes

codon_plan — goal to queue (Plus)

—Yes

Local-first by design

The queue, the brief and your usage records stay in your project, on your machine.

Codon works with the coding accounts and project files you already control. The server makes no network calls of its own and doesn't proxy model requests. It never copies or sends a provider's sign-in — it only checks each CLI's own files to report whether you're signed in.

codon_plan runs through CodonTerminal, which checks your Gattaca key with the license endpoint. Only the key is sent, never project data, and a good answer is trusted for a day.

Ready when your agents are

Give every agent the same queue.

Install Codon free, queue work from any agent, and let CodonTerminal run it on the subscriptions you already pay for.

Install Codon MCPOpen your account

A look at the browser Command Center

Development preview with simulated tasks and runs. Remote access from another device isn't available yet: today the Command Center is served by CodonTerminal on your own computer. This preview is separate from the available MCP tools above and is not a hosted execution service.

Full size ↗Motion paused
Codon Command CenterDevelopment preview · simulated runs

Explore the workflow

Actual app screens with sample data. Choose a step to take a closer look.

Codon Command Center: See the work take shape.

See the work take shape.

Preview the browser workspace being developed for a runner on your own computer.

View full-size screen (opens a new tab)