Bugsink

You can use Bugsink MCP Server to query and analyze your Bugsink error tracking data from AI assistants and MCP-compatible clients. It provides a streamlined set of endpoints to list projects, teams, and issues, as well as to fetch detailed information about specific issues and events.

How to use

You interact with Bugsink MCP Server through your MCP client or integrated AI assistant. Start by ensuring the server is running locally or reachable via HTTP, then issue natural language requests like: “List all projects in Bugsink,” “Show the latest issues for project 1,” or “What is the stacktrace for issue #42?” The MCP server translates these prompts into specific actions such as listing projects, listing issues for a project, or retrieving detailed event data. Use the available actions to drill into error details, view stack traces, or verify your connection before querying data.

How to install

# Prerequisites: Node.js and npm must be installed on your system

# Install the MCP server via npx (recommended)
npx bugsink-mcp

# Or install as a global CLI
npm install -g bugsink-mcp

# From source: clone the repository, install dependencies, and build
git clone https://github.com/j-shelfwood/bugsink-mcp.git
cd bugsink-mcp
npm install
npm run build

# Generate an API token for Bugsink access
bugsink-manage create_auth_token

Or create tokens via the Bugsink web UI under Settings > API Tokens.

## Configuration and usage notes

Environment variables are required for authenticating with Bugsink. You must provide BUGSINK\_URL and BUGSINK\_TOKEN to the MCP server or your client environment.

Client configuration examples show how to wire the MCP server into your AI assistants. Each example sets the MCP server location and authentication details.

{ "mcpServers": { "bugsink": { "command": "npx", "args": ["bugsink-mcp"], "env": { "BUGSINK_URL": "https://your-bugsink-instance.com", "BUGSINK_TOKEN": "your-api-token" } } } }

## Client setup for Claude Desktop

Add the MCP server configuration to your Claude Desktop settings so Claude can access Bugsink data.

{ "mcpServers": { "bugsink": { "command": "npx", "args": ["bugsink-mcp"], "env": { "BUGSINK_URL": "https://your-bugsink-instance.com", "BUGSINK_TOKEN": "your-api-token" } } } }

## Client setup for Claude Code CLI

In Claude Code CLI, add Bugsink MCP as a server and supply the command to run.

claude mcp add bugsink -- npx bugsink-mcp

Then set environment variables in your shell or in a .env file.

Client setup for Cursor

Configure Cursor to connect to Bugsink via MCP using a local stdio server.

{
  "mcpServers": {
    "bugsink": {
      "command": "npx",
      "args": ["bugsink-mcp"],
      "env": {
        "BUGSINK_URL": "https://your-bugsink-instance.com",
        "BUGSINK_TOKEN": "your-api-token"
      }
    }
  }
}

Available endpoints and actions

The server exposes endpoints to perform common error-tracking tasks such as listing projects, listing teams, listing issues for a project, getting issue details, listing events for an issue, and retrieving full event details.

Notes and best practices

• Ensure your Bugsink URL is reachable from the environment where you run the MCP server. - Protect your API token and rotate it regularly. - Use the test connection action to verify connectivity before querying data.

Troubleshooting

If you encounter authentication or connectivity issues, verify the BUGSINK_URL and BUGSINK_TOKEN values are correct in your environment and that the Bugsink instance is accessible from your network.

Notes

This MCP server is designed to work with Bugsink and its REST API. It is not compatible with Sentry or Sentry-hosted services. For Sentry, use the official Sentry MCP server instead.

Available tools

list_projects

List all projects in the Bugsink instance.

list_teams

List all teams in the Bugsink instance.

list_issues

List issues for a specific project with optional status and limit filters.

get_project

Get detailed information about a specific project including DSN.

get_issue

Get detailed information about a specific issue.

list_events

List events (individual error occurrences) for a specific issue.

get_event

Get detailed event information including full stacktrace.