MCP server for testing

The MCP server connects AI coding tools — Claude Code, Cursor, Codex — to BugBrain, so your assistant can start runs, read issues, and more without leaving your editor. This guide covers the two ways to connect and how to configure each.

What it is#

MCP (the Model Context Protocol) is an open standard for giving AI assistants access to external tools. BugBrain's MCP server speaks that protocol, so any MCP-capable tool can call BugBrain's capabilities directly. There are two ways to run it:

• Local stdio bridge — a small process that runs on your machine via npx, ideal for a single developer.
• Hosted Streamable-HTTP — a remote endpoint you point a client at, with nothing to install.

Both authenticate with an sk_live_ API key and expose the same tools — and only the tools your key's scopes permit.

Why use it#

• QA in your IDE — ask your assistant to start a run or summarize open issues, and it talks to BugBrain for you.
• Scoped by your key — the assistant can only do what the API key allows, so you stay in control.
• Standard and portable — any MCP-capable client works the same way; the package is open source on npm.

Before you start#

• Create an sk_live_ API key with the access you want — the MCP Purpose preset for full access, or a narrower one to restrict the assistant. See API keys.
• For the local bridge, you need Node.js (so npx is available).

Option A — local stdio bridge#

Run the published package via npx and authenticate with the BUGBRAIN_API_KEY environment variable (your sk_live_ key).

1. 1

   Add the server to your client

   In your tool's MCP config, register a server that runs the bridge.
2. 2

   Provide your API key

   Pass your sk_live_ key as the BUGBRAIN_API_KEY environment variable.
3. 3

   Reload and use

   Restart or reload your tool; its MCP tool list now includes BugBrain.

A typical MCP client config (the shape most tools, including Claude Code and Cursor, accept):

{
  "mcpServers": {
    "bugbrain": {
      "command": "npx",
      "args": ["-y", "@bugbrain/mcp"],
      "env": {
        "BUGBRAIN_API_KEY": "sk_live_your_key_here"
      }
    }
  }
}

Option B — hosted Streamable-HTTP#

Point your client at the hosted endpoint and authenticate with a bearer header — nothing to install.

• URL: https://mcp.bugbrain.tech/mcp
• Header: Authorization: Bearer sk_live_…

A typical remote-server config:

{
  "mcpServers": {
    "bugbrain": {
      "url": "https://mcp.bugbrain.tech/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Tips#

• Use a dedicated MCP key per machine or tool, so you can revoke one without disrupting the others.
• The package is open source — @bugbrain/mcp on public npm (MIT), listed on the MCP Registry as tech.bugbrain/mcp.
• Store the key in your tool's secret/config mechanism, not in a checked-in file.

Related#