Bugsink MCP Server

A professional Model Context Protocol (MCP) server for interacting with Bugsink error tracking instances. Designed for LLM-powered workflows in Claude, Cursor, OpenCode, and any other MCP-compatible client.

Features

• Projects: list, inspect, create, and update projects.
• Teams: list, create, and update teams.
• Issues: list, inspect, change status (resolve / mute / unresolve), and get holistic analysis with recent events and stacktraces.
• Events: list, inspect, get raw JSON, and get pre-rendered Markdown stacktraces.
• Releases: list, inspect, and create releases.
• Connection testing: built-in test_connection tool.
• Bilingual: English and Spanish support via BUGSINK_LOCALE.

Requirements

• Node.js 18+
• A Bugsink instance with API access (Bugsink 2.0+ recommended)
• A Bugsink API token

Installation

From npm (recommended)

npm install -g @alvaroadlf/bugsink-mcp

From source

git clone https://github.com/alvaroadlf/bugsink-mcp.git
cd bugsink-mcp
npm install
npm run build

Configuration

Set these environment variables in your MCP client configuration:

{
  "mcp": {
    "bugsink": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@alvaroadlf/bugsink-mcp"
      ],
      "enabled": true,
      "environment": {
        "BUGSINK_URL": "https://bugsink.example.com",
        "BUGSINK_TOKEN": "your-api-token",
        "BUGSINK_LOCALE": "en"
      }
    }
  }
}

| Variable | Required | Description | |----------|----------|-------------| | BUGSINK_URL | Yes | URL of your Bugsink instance | | BUGSINK_TOKEN | Yes | API token from Bugsink | | BUGSINK_LOCALE | No | en (default) or es |

OpenCode example

In opencode.jsonc:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bugsink": {
      "type": "local",
      "command": [
        "node",
        "/absolute/path/to/bugsink-mcp/dist/index.js"
      ],
      "enabled": true,
      "environment": {
        "BUGSINK_URL": "https://bugsink.example.com",
        "BUGSINK_TOKEN": "{env:BUGSINK_TOKEN}"
      }
    }
  }
}

Using {env:BUGSINK_TOKEN} keeps your token out of the config file.

Available Tools

| Tool | Description | |------|-------------| | test_connection | Verify connectivity to the Bugsink instance | | list_projects | List all projects | | get_project | Get project details including DSN | | create_project | Create a new project | | update_project | Update project settings | | list_teams | List all teams | | get_team | Get team details | | create_team | Create a new team | | update_team | Update a team | | list_issues | List issues for a project, filterable by status | | get_issue | Get issue details | | update_issue_status | Resolve, mute, or unresolve an issue | | analyze_issue_context | Holistic analysis: issue + recent events + stacktrace | | project_issue_summary | Summary of unresolved/resolved/muted issues | | list_events | List events for an issue | | get_event | Get event details including stacktrace | | get_event_raw | Get raw event JSON | | get_stacktrace | Get pre-rendered Markdown stacktrace | | list_releases | List releases for a project | | get_release | Get release details | | create_release | Create a new release |

Usage examples

List unresolved issues

"Show me the unresolved issues for project 1 in Bugsink."

Analyze an issue

"Analyze issue a29dfc3a-c1ce-4dba-acb1-2bb7168cb07c in Bugsink."

Mark an issue as resolved

"Resolve issue a29dfc3a-c1ce-4dba-acb1-2bb7168cb07c in Bugsink."

Get project summary

"Give me an issue summary for the Freefy Web App project."

Development

npm install
npm run build
npm run dev      # watch mode
npm test         # run tests when available

Run the integration test against your instance:

export BUGSINK_URL=https://bugsink.example.com
export BUGSINK_TOKEN=your-token
bash test-integration.sh

License

MIT © Alvaro Araoz