Bounty MCP

Bounty MCP is an MCP server that enforces a strict, review-driven coding workflow for iterative implementation with subagents.

It is designed for one job: run a task in controlled rounds, keep a protocol trail, and end with an explicit accept/reject decision.

What This Tool Is

• A workflow controller for coding tasks, not a general chatbot.
• A branch-based protocol around bounty/* branches.
• A guardrail system that keeps rounds explicit and auditable (BOUNTY.md, BOUNTY_TRACE.md).

Workflow

The lifecycle is fixed:

bounty -> [steer x N] -> verdict

1) bounty (initiate, once)

• Creates bounty/<title> branch.
• Writes protocol files and starts Round 1.
• Requires a clean working tree.
• Hard rule: align with the human on both humanGoal and task before starting. If either is unclear, do not start.

2) steer (iterate, repeatable)

• Adds review feedback and starts the next round.
• Can be called multiple times until the work is ready.

3) verdict (finalize, once)

• DONE: merge to base branch and clean bounty branch.
• DROP: discard and clean bounty branch.
• Hard rule: review code and diff before verdict. No review, no verdict.

MCP Configuration

Option A: stdio transport (default, via npm)

Recommended MCP server config:

{
  "mcpServers": {
    "bounty": {
      "command": "npx",
      "args": ["-y", "bounty-mcp"],
      "env": {
        "BOUNTY_MCP_TRANSPORT": "stdio"
      }
    }
  }
}

Option B: stdio transport (local build)

Build first:

npm install
npm run build

Run server:

node build/index.js

Minimal MCP server config:

{
  "mcpServers": {
    "bounty": {
      "command": "node",
      "args": ["/absolute/path/to/bounty-mcp/build/index.js"],
      "env": {
        "BOUNTY_MCP_TRANSPORT": "stdio"
      }
    }
  }
}

Option C: streamable HTTP transport

Run server:

BOUNTY_MCP_TRANSPORT=streamable-http BOUNTY_MCP_HTTP_HOST=127.0.0.1 BOUNTY_MCP_HTTP_PORT=3000 node build/index.js

Server endpoint:

http://127.0.0.1:3000/mcp

Available Tools

bounty

Starts a new task round.

Main inputs:

• title, task, criteria (required)
• context, constraints, minionName, cwd (optional)

steer

Provides feedback and launches the next round.

Main inputs:

• directive (required)
• context, minionName, cwd (optional)

verdict

Closes the lifecycle with DONE or DROP.

Main inputs:

• result, reasons, metPrecise, metMinimal, metIsolated, metIdiomatic, metCohesive, oath (required)
• cwd (optional)

Protocol Files

• BOUNTY.md: immutable mission definition for the task.
• BOUNTY_TRACE.md: round-by-round execution and review trace.

These files are core to workflow continuity and final evaluation.