# Pitroom MCP server

> Delegates reading, fixes, tests, and reviews to cheaper parallel worker agents, returning verified answers, exact diffs, and cost receipts.

- Repository: https://github.com/ATASTECH/pitroom
- Page: https://hostedmcp.org/servers/atastech/pitroom
- Transport: stdio
- Stars: 53
- License: MIT
- Latest version: 0.29.0

## Install

### Claude Code

```sh
claude mcp add pitroom -- npx -y pitroom
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "pitroom": {
      "command": "npx",
      "args": [
        "-y",
        "pitroom"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "pitroom": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "pitroom"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"pitroom","type":"stdio","command":"npx","args":["-y","pitroom"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "pitroom": {
      "command": "npx",
      "args": [
        "-y",
        "pitroom"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add pitroom -- npx -y pitroom
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.pitroom]
command = "npx"
args = ["-y", "pitroom"]
```

### Gemini CLI

```sh
gemini mcp add -s user pitroom npx -- -y pitroom
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "pitroom": {
      "command": "npx",
      "args": [
        "-y",
        "pitroom"
      ]
    }
  }
}
```

## Tools (10)

- `pitroom_run`: Hand a bounded task to a cheaper worker agent. mode "read" (default): read-only research, an answer with verified file:line references. "isolate": the worker edits a private copy and you get the exact diff (then pitroom_review, pitroom_apply or pitroom_discard). "write": edits the working tree (undo: pitroom_revert). "tasks" or "scopes" run workers in parallel (read or isolate). Returns the report(s) and a receipt (a read question asked before on the same code comes back cached), or "still running" for pitroom_wait. The using-pitroom skill (or prompt) says when and how to delegate. Cancelling the call stops the run.
- `pitroom_wait`: Wait for runs that came back "still running" and return their reports. (read-only)
- `pitroom_show`: A run's report (live progress while it runs); patch: the exact diff; full: the untruncated answer. (read-only)
- `pitroom_info`: Reports, changing nothing. topic: runs (latest runs; running, group), history (search earlier answers before asking again; text, state, model, since, limit), stats (success rate, time, tokens, audits per worker; since), savings (since, perModel), models (a backend's models and costs; worker, all), prices (USD per 1M tokens: the primary the savings are measured against, and each worker in use or the one named; worker), cooldown (rate-limited models being skipped), config, doctor (setup check). (read-only)
- `pitroom_review`: A read-only reviewer (another worker by default) judges a run's change or a commit range ("main..HEAD"): findings with severities and a SPEC / QUALITY verdict.
- `pitroom_audit`: Another worker re-checks a read run's answer: AGREE, PARTIAL or DISAGREE, with the disputed claims.
- `pitroom_apply`: Land an isolated run's patch (or a group's, in order) on the working tree; checked first. A patch deleting files needs allowDelete: pass it only after checking the deletions were asked for.
- `pitroom_discard`: Drop an isolated run's private copy (the patch is kept).
- `pitroom_revert`: Undo a mode "write" run's changes (refused if the files changed since).
- `pitroom_stop`: Stop a running or queued run, or a group; cooldowns: try rate-limited models again now.

## FAQ

### Does Pitroom require a specific AI model?

No. Pitroom uses whichever default model your worker CLI is set to, from a free tier to a local or paid model.

### Which worker CLIs can Pitroom use?

It supports OpenCode, Codex CLI, Claude Code, Gemini CLI, Qwen Code, Kilo Code, Antigravity CLI and Cursor CLI. A single group can mix several of them.

### Can Pitroom make changes to my repository?

Workers can produce patches, but Pitroom never commits or pushes, and in isolate mode nothing reaches your tree until you apply it.

### How does Pitroom prevent a worker from editing files directly?

Each run uses the worker's own permission rules to block git history changes, sudo, publishing and secrets, and a git guard blocks tricks like shell-wrapped git commands.

### Is there a dashboard for watching runs?

Yes, `pitroom dash` serves a local page showing running workers, run history and statistics.
