Pursers MCP server

Chat dies. The board doesn't.

Not another MCP. The OS for AI agent work.

One local board runs a whole agent fleet — any model, any MCP client. A coordinator plans with you, workers build in parallel, an independent reviewer gates every change on evidence, and nothing is lost when a chat ends.

Quickstart · How a ticket moves · What's in the box · Docs · pursers.app

main: 5.0.3

[!IMPORTANT]

Pursers was built by its own fleet. From first commit to 5.0.0 on PyPI and

the MCP Registry took 27 days. The board ran 542 tickets through

37 worker seats and 19 reviewer seats; reviewers sent work back

575 times before approving it; and every release push had to pass a

2,660-test gate. One human set the direction and made the calls.

How a ticket moves

Step by step, as MCP tool calls

sequenceDiagram
    autonumber
    actor You
    participant C as Coordinator
    participant B as Board (Central)
    participant W as Worker
    participant R as Reviewer
    You->>C: intent
    C->>B: ticket_create
    B-->>W: offer — wakes the waiting seat
    W->>B: ticket_claim — lease starts
    Note over W: builds in its own checkout,<br/>renews the lease
    W->>B: ticket_submit — commit, files, test output
    B-->>R: review offer
    alt evidence holds
        R->>B: approve
    else evidence falls short
        R->>B: reject with fix instructions
        B-->>W: back to the same worker
    end
    B-->>You: approved work, ready to merge

Recorded from the real product — the Fleet dashboard following one ticket on a disposable board, from offer to independent approval:

Why it sticks

Shortened. The full README is on GitHub.