The BetterBugs MCP server lets AI agents (Claude, Cursor, Windsurf, etc.) read bug reports directly from your BetterBugs workspace — including screenshots, console logs, and network requests — so they can diagnose and fix issues without you copy-pasting anything.
Instead of manually pulling data from BetterBugs and pasting it into your AI chat, the server gives the agent direct access. You share a bug link, the agent fetches the full context, and you go straight to the fix.
| Tool | Description |
|---|---|
getUserDetails |
Returns the authenticated user's profile, workspaces, and account info |
listWorkspaces |
Lists all workspaces the user has access to |
listProjects |
Lists projects inside a given workspace (workspace_id required) |
listBugs |
Lists bugs for a project with status, priority, and summaries (project_id required) |
getBugDetails |
Fetches the full bug report — title, description, status, priority, and visual evidence |
getScreenshot |
Retrieves the screenshot attached to a bug report (call after getBugDetails) |
getBugLogs |
Retrieves console logs, network requests, and user interaction events for a bug |
Server URL: https://mcp.betterbugs.io/mcp
Transports supported:
- Streamable HTTP (modern) —
POST/GET/DELETE /mcp - Server-Sent Events (legacy) —
GET /sse+POST /message
See client-configs.md for ready-to-paste config snippets.
The server uses OAuth 2.0 with PKCE. When you first connect, a browser window opens asking you to authorize the server to access your BetterBugs account. After that, the token is managed automatically — no API keys to copy.
Your MCP client must send requests with an Authorization: Bearer <token> header. Clients that support OAuth (VS Code, Cursor, Claude Code, etc.) handle this for you after the initial login.
Access level mirrors your existing BetterBugs permissions — the agent can only see what you can see.
- Docs: https://docs.betterbugs.io/debug-a-report/mcp
- BetterBugs: https://betterbugs.io