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, with permissions and project counts |
listProjects |
Lists projects inside a given workspace, paginated (workspace_id required) |
listBugs |
Lists bugs for a project (newest-first, paginated) with optional filters for priority, status, creator, assignees, tags, integrations, source, and date range (workspace_id + project_id required) |
getBugDetails |
Fetches the full bug report — title, description, status, priority, and visual evidence; can also include comments and viewers (bug_id required) |
getScreenshot |
Retrieves the screenshot attached to a bug report as base64 (call after getBugDetails, bug_id required) |
getBugLogs |
Retrieves console logs, network requests, and user interaction events for a bug (bug_id required) |
getVideoAnalysis |
Returns AI analysis of a bug's screen recording — summary, results, and a hasSpeech flag (workspace_id + bug_id required) |
getTranscription |
Returns the audio transcription of a bug's screen recording (workspace_id + bug_id required) |
| Tool | Description |
|---|---|
shareBug |
Invites a person to a bug by email, with optional time-limited access |
updateBugDetails |
Updates a bug's title, description, status, priority, tags, assignee, metadata, comments (with @-mentions), project transfer, or archive state |
managemembersinworkspace |
Manages workspace members — list, invite, change role, remove (via action) |
manageprojectinworkspace |
Manages projects — create, update, change privacy/session visibility, add member (via action) |
recordingLink |
Manages shareable browser-based bug recording links — list, create, update, delete, get_bugs (via action) |
| Tool | Description |
|---|---|
basecamp |
Push a bug to Basecamp — list organizations/projects/columns/assignees, then send_bug (via action) |
jira |
Create a Jira issue from a bug — list sites/projects/issue types/fields/assignees/labels/boards/sprints, then send_bug (via action) |
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