MCP server

$ claude mcp add --transport http devbench https://api.developerbench.com/mcp \
  --header "Authorization: Bearer dbk_…"

{
  "mcpServers": {
    "devbench": {
      "url": "https://api.developerbench.com/mcp",
      "headers": {
        "Authorization": "Bearer dbk_…"
      }
    }
  }
}

{
  "mcpServers": {
    "devbench": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.developerbench.com/mcp",
        "--header",
        "Authorization:${DEVBENCH_AUTH}"
      ],
      "env": {
        "DEVBENCH_AUTH": "Bearer dbk_…"
      }
    }
  }
}

Endpoint: https://api.developerbench.com/mcp, MCP Streamable HTTP transport, authenticated with the same Authorization: Bearer dbk_… header on every request. No OAuth. Stateless: no session state is needed beyond the key.

• A missing or bad key is HTTP 401 (as for /v1), before any JSON-RPC.
• 503 (disabled) and 429 (rate limited, Retry-After) are HTTP statuses too.
• Inside a valid session, a tool that fails (402, 403, 404, 400, 409, 502 above) returns a tool result with isError: true and the same error sentence as its text, so the client's AI can read and act on it.

Tools map one-to-one onto routes and call the same handler code with the same scope, edition, entitlement and audit rules. Arguments are the route's path and query parameters (and body fields for writes), with the same names, types and limits. Results are the route's JSON as structuredContent, plus one text block: a one-line summary followed by the JSON.

Tool	Route	Scope
list_issues	GET /v1/issues	issues:read
get_issue	GET /v1/issues/{id}	issues:read
top_errors	GET /v1/errors/top	sensors:read
error_trend	GET /v1/fingerprints/{id}/trend (argument fingerprint_id)	sensors:read
release_impact	GET /v1/releases/{release}/impact	sensors:read
find_user	GET /v1/users	users:read
issue_users	GET /v1/issues/{id}/users	users:read
issue_logs	GET /v1/issues/{id}/logs	logs:read
issue_evidence	GET /v1/issues/{id}/evidence	logs:read
resolve_issue	POST /v1/issues/{id}/resolve	issues:write (V2)
dismiss_issue	POST /v1/issues/{id}/dismiss	issues:write (V2)
reopen_issue	POST /v1/issues/{id}/reopen	issues:write (V2)
comment_on_issue	POST /v1/issues/{id}/comments	issues:write (V2)

Path ids are the argument id (an integer), except error_trend (fingerprint_id) and release_impact (release). GET /v1/me has no tool; a client that needs it calls the route.

• tools/list returns only the tools the key can use (its usable scopes): a V1 read key never sees a write tool. While billing has lapsed the list is unchanged and calls return the 402 error.
• Tool descriptions are written for an AI reader: what the tool returns, units (counts are occurrences; per_day_* are occurrences per day), and that every time is UTC.
• The test suite fails if a /v1 route has no tool or a tool has no route (other than /v1/me).