Bugsink MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUGSINK_URL | Yes | Your Bugsink instance URL (e.g., https://error-tracking.example.com) | |
| BUGSINK_TOKEN | Yes | API token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List all projects in the Bugsink instance |
| list_teamsB | List all teams in the Bugsink instance |
| list_issuesC | List issues for a specific project. Issues represent grouped error occurrences. |
| get_issueC | Get detailed information about a specific issue |
| list_eventsC | List events (individual error occurrences) for a specific issue. Returns basic event info. |
| get_eventB | Get detailed information about a specific event, including full stacktrace and context |
| test_connectionB | Test the connection to the Bugsink instance |
| get_projectB | Get detailed information about a specific project including DSN |
| create_projectC | Create a new project in a team |
| update_projectC | Update an existing project's settings |
| create_teamC | Create a new team |
| update_teamC | Update an existing team |
| get_stacktraceB | Get an event's stacktrace as pre-rendered Markdown. More readable than raw frame data. |
| list_releasesC | List releases for a project. Releases help track which version introduced or fixed issues. |
| get_releaseC | Get detailed information about a specific release |
| create_releaseC | Create a new release for a project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.