@feedbug/mcp

Visual bug reports your AI agent can actually fix.

Feedbug lets your testers report bugs by clicking on them. Each report captures a screenshot, the console logs, the failed network requests, a session replay, and the HTML/DOM context of the element they clicked, then opens an issue in your Linear project or your GitHub repository automatically. When a code source is connected, the issue also carries a link to the source file the bug most likely came from.

This MCP server plugs that data straight into your AI coding agent (Claude Code, Cursor, Windsurf, VS Code). The agent reads the bug, gets the exact CSS selector and component path, traces it to the source file, proposes the patch, and marks the bug resolved.

Full write-up of the product side: feedbug.app/mcp-bug-tracking.

Point at the bug. Ship the fix.

Quick start

npx @feedbug/mcp init

The installer asks for your client and your project key, then writes the config for you. Non-interactive:

npx @feedbug/mcp init --client claude pk_your_project_key

Supported clients: claude (Claude Code), cursor, windsurf. Grab your project key (pk_...) from your project page on feedbug.app.

Restart your client and the tools are live.

Related MCP server: Skippr Extension MCP Server

Manual configuration

Add this to your client's MCP config (.mcp.json, .cursor/mcp.json, .windsurf/mcp.json, etc.):

{
  "mcpServers": {
    "feedbug": {
      "command": "npx",
      "args": ["-y", "@feedbug/mcp"],
      "env": {
        "FEEDBUG_API_URL": "https://api.feedbug.app",
        "FEEDBUG_PROJECT_KEY": "pk_your_project_key"
      }
    }
  }
}

Run with Docker

docker build -t feedbug-mcp .

{
  "mcpServers": {
    "feedbug": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "FEEDBUG_PROJECT_KEY", "feedbug-mcp"],
      "env": {
        "FEEDBUG_PROJECT_KEY": "pk_your_project_key"
      }
    }
  }
}

Environment variables

Tools

Every tool accepts either the feedback UUID or the tracker identifier (e.g. PRE-13 on Linear, owner/repo#42 on GitHub).

How it works

When a tester clicks a bug, the Feedbug widget snapshots the DOM around the clicked element: the CSS selector path, the framework component name when detectable, the element's attributes and text, plus its ancestors and siblings. That snapshot travels with the Linear ticket.

Through this MCP server, your agent reads that context and maps the bug to the exact file and line, instead of guessing from a vague "it's broken on the dashboard" description.

Links

• Product: feedbug.app

• API: https://api.feedbug.app

License

MIT