Bugsink MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bugsink MCP Server list the latest unresolved issues for project 123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bugsink MCP Server
A Model Context Protocol server for interacting with Bugsink error tracking via LLMs.
This server enables AI assistants like Claude, Cursor, and other MCP-compatible tools to query and analyze errors from your Bugsink instance.
Features
List Projects - View all projects in your Bugsink instance
List Teams - View all teams
List Issues - Query grouped error occurrences by project
Get Issue Details - Retrieve detailed issue information
List Events - View individual error occurrences with stacktraces
Get Event Details - Full event data including tags and contexts
Test Connection - Verify API connectivity
Related MCP server: GlitchTip MCP Server
Installation
Via npx (Recommended)
npx bugsink-mcpGlobal Install
npm install -g bugsink-mcpFrom Source
git clone https://github.com/j-shelfwood/bugsink-mcp.git
cd bugsink-mcp
npm install
npm run buildConfiguration
Environment Variables
Variable | Required | Description |
| Yes | Your Bugsink instance URL (e.g., |
| Yes | API token for authentication |
Generating an API Token
# Via Bugsink management command
bugsink-manage create_auth_tokenOr through the Bugsink web UI under Settings > API Tokens.
MCP Client Configuration
Claude Desktop
Add to your Claude Desktop configuration (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"bugsink": {
"command": "npx",
"args": ["bugsink-mcp"],
"env": {
"BUGSINK_URL": "https://your-bugsink-instance.com",
"BUGSINK_TOKEN": "your-api-token"
}
}
}
}Claude Code CLI
claude mcp add bugsink -- npx bugsink-mcpThen set environment variables in your shell or .env file.
Cursor
Add to your Cursor MCP settings:
{
"mcpServers": {
"bugsink": {
"command": "npx",
"args": ["bugsink-mcp"],
"env": {
"BUGSINK_URL": "https://your-bugsink-instance.com",
"BUGSINK_TOKEN": "your-api-token"
}
}
}
}Available Tools
test_connection
Test connectivity to your Bugsink instance.
list_projects
List all projects in the Bugsink instance.
get_project
Get detailed information about a specific project including DSN.
Parameters:
project_id(number, required): The project ID
list_teams
List all teams in the Bugsink instance.
list_issues
List issues for a specific project.
Parameters:
project_id(number, required): The project IDstatus(string, optional): Filter by status ('unresolved', 'resolved', 'muted')limit(number, optional): Max results (default: 25)
get_issue
Get detailed information about a specific issue.
Parameters:
issue_id(number, required): The issue ID
list_events
List events (individual error occurrences) for a specific issue.
Parameters:
issue_id(number, required): The issue IDlimit(number, optional): Max results (default: 10)
get_event
Get detailed event information including full stacktrace.
Parameters:
event_id(string, required): The event ID
Example Usage
Once configured, you can ask your AI assistant:
"List all projects in Bugsink"
"Show me the latest issues for project 1"
"What's the stacktrace for issue #42?"
"Get the details of the most recent error event"
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build for production
npm run build
# Run tests
npm testAPI Compatibility
This server is designed for Bugsink, a self-hosted error tracking platform. Bugsink uses its own REST API (/api/canonical/0/) which is different from Sentry's API.
Note: This server does NOT work with Sentry or Sentry-hosted services. For Sentry, use the official sentry-mcp server.
License
MIT
Contributing
Contributions welcome! Please open an issue or PR on GitHub.
Available Tools
16 toolscreate_projectC
Create a new project in a team
Inputs: team_id (required), name (required), visibility, alert_on_new_issue, +2 more.
create_releaseC
Create a new release for a project
Inputs: project_id (required), version (required), timestamp.
create_teamC
Create a new team
Inputs: name (required), visibility.
get_eventB
Get detailed information about a specific event, including full stacktrace and context
Inputs: event_id (required).
get_issueC
Get detailed information about a specific issue
Inputs: issue_id (required).
get_projectB
Get detailed information about a specific project including DSN
Inputs: project_id (required).
get_releaseC
Get detailed information about a specific release
Inputs: release_id (required).
get_stacktraceB
Get an event's stacktrace as pre-rendered Markdown. More readable than raw frame data.
Inputs: event_id (required).
list_eventsC
List events (individual error occurrences) for a specific issue. Returns basic event info.
Inputs: issue_id (required), limit.
list_issuesC
List issues for a specific project. Issues represent grouped error occurrences.
Inputs: project_id (required), status, limit, sort, +1 more.
list_projectsB
List all projects in the Bugsink instance
Inputs: no named parameters.
list_releasesC
List releases for a project. Releases help track which version introduced or fixed issues.
Inputs: project_id (required).
list_teamsB
List all teams in the Bugsink instance
Inputs: no named parameters.
test_connectionB
Test the connection to the Bugsink instance
Inputs: no named parameters.
update_projectC
Update an existing project's settings
Inputs: project_id (required), name, visibility, alert_on_new_issue, +3 more.
update_teamC
Update an existing team
Inputs: team_id (required), name, visibility.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, 'get_event' retrieves event details while 'list_events' lists events for an issue, and 'get_stacktrace' provides formatted stacktraces distinct from raw event data.
All tools follow a consistent verb_noun pattern throughout, using lowercase with underscores. The naming is predictable with verbs like 'create', 'get', 'list', 'update', and 'test' paired with specific nouns like 'project', 'issue', or 'team'.
With 16 tools, the count is slightly high but reasonable for a bug/error tracking system covering teams, projects, issues, events, releases, and connections. It feels comprehensive without being overwhelming, though it borders on the heavier side of typical scopes.
The tool set provides complete CRUD/lifecycle coverage for the Bugsink domain, including create, get, list, and update operations for teams, projects, issues, events, and releases, plus connection testing. There are no obvious gaps, enabling agents to handle full workflows without dead ends.
Maintenance
Related MCP Connectors
Let AI agents list, read and resolve Bugsly error-tracking issues and check monitors.
Query your app's logs, metrics and incidents from your AI assistant.
Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.
Production bugs with replay, network, console and stack, ranked for your coding agent to fix.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with Glitchtip error tracking platform through natural language. Provides access to issues, events, projects, teams, and organization management for comprehensive error monitoring and debugging.718 npm3AGPL 3.0
- AlicenseAqualityDmaintenanceEnables AI assistants to query, analyze, and resolve errors within the GlitchTip error tracking platform by providing access to issue details and stacktraces. It allows users to list unresolved issues and mark them as fixed using natural language commands.322 PyPI2MIT
- AlicenseBqualityDmaintenanceIntegrates GlitchTip error monitoring with AI assistants to fetch, analyze, and debug production errors. It enables users to list issues, retrieve event details, and perform guided triage of application errors through natural language.2259 npm11MIT
- AlicenseBqualityDmaintenanceIntegrates GlitchTip error monitoring with AI assistants, enabling them to fetch, analyze, and debug issues from your GlitchTip instance.221 npm5MIT