RunbookHQ

Opening workbench
RunbookHQ

Editors

MCP for your editor

A personal token on Account connects Cursor, Claude, ChatGPT, or Codex. Same access you have. The hosted server never runs scripts or generator code.

  1. Create a personal token

    Sign in, open Account → MCP, and create a token. The plaintext is shown once. Copy the setup snippet then; later you rotate by creating a new token.

  2. Point the editor at the server

    URL https://runbookhq.app/api/mcp with Authorization: Bearer rbhq_…. Cursor uses ~/.cursor/mcp.json. Claude Code uses claude mcp add --transport http. ChatGPT and Codex have their own connectors.

  3. Same access you have

    Membership, module grants, named groups, and restricted folders apply. Org policy can cap MCP at off, read, or write. The server searches and can upsert report kits; it never executes generator code or script bytes.

Cursor example

{
  "mcpServers": {
    "runbookhq": {
      "url": "https://runbookhq.app/api/mcp",
      "headers": {
        "Authorization": "Bearer rbhq_…"
      }
    }
  }
}

Claude, ChatGPT, and Codex use the same URL and bearer token. After you create a token, Account → MCP shows the snippet for the editor you pick. Editors we document: Cursor, Claude, ChatGPT, Codex.