IndieBob as MCP tools. Read your metrics, draft and publish posts, list prospects, enrol them in an outreach sequence, read the review queue, approve a first touch, and ask what to do next — from any MCP client.

Install

Nothing to install. Add this to your MCP client config:

{
  "mcpServers": {
    "indiebob": {
      "command": "npx",
      "args": ["-y", "@indiebob/mcp"],
      "env": {
        "INDIEBOB_API_KEY": "ib_sk_…",
        "INDIEBOB_BASE_URL": "https://indiebob.com"
      }
    }
  }
}

INDIEBOB_BASE_URL is optional and defaults to https://indiebob.com.

Claude Code: claude mcp add indiebob --env INDIEBOB_API_KEY=ib_sk_… -- npx -y @indiebob/mcp

The key

Service keys are minted by the account owner and carry explicit scopes. A key for every tool here needs:

read:projects, read:metrics, read:actions, read:content, write:content, read:outreach, write:outreach.

Grant less and the rest still works — a tool that needs a scope you did not grant answers with the scope's name so you can ask for exactly that one.

See https://indiebob.com/docs/agents to mint one, and https://indiebob.com/agents.md for the full capability document (this server's tools are generated from it).

Tools

Tool	Does
`whoami`	Check the key and list its scopes
`list_projects`	Every project, with health and stage
`read_metrics`	Daily MRR / visitors / signups snapshots
`next_actions`	The ranked "what should I do next" feed
`list_posts` / `get_post`	Blog posts and one post's markdown
`create_post` / `publish_post`	Draft and publish
`list_prospects`	Cold-outreach prospects for a project
`list_sequences`	Sequences, with whether each is personalised
`enroll_prospects`	Enrol prospects into a sequence
`list_review_queue`	First touches waiting for a human yes
`approve_message`	Approve one first touch

What it will not do

Billing, key minting, project creation and settings stay in the browser. Approving a first touch does not send it — the sequence's send window, daily cap and sending account still apply.

MIT.