GlitchTip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLITCHTIP_TOKEN | No | GlitchTip API token. Either GLITCHTIP_TOKEN or GLITCHTIP_SESSION_ID is required. | |
| GLITCHTIP_BASE_URL | No | The URL of your GlitchTip instance. | https://app.glitchtip.com |
| GLITCHTIP_SESSION_ID | No | GlitchTip session cookie value. Either GLITCHTIP_TOKEN or GLITCHTIP_SESSION_ID is required. | |
| GLITCHTIP_ORGANIZATION | No | Your GlitchTip organization slug. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glitchtip_issuesC | Get all issues from GlitchTip |
| glitchtip_latest_eventB | Get the latest event for a specific issue |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recent_errors | Get overview of recent production errors with analysis and prioritization |
| debug_issue | Deep-dive into a specific error with full context and suggest fixes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GlitchTip Issues | All unresolved issues from GlitchTip error monitoring |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves all issues, while the other fetches the latest event for a specific issue. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent naming pattern with the prefix 'glitchtip_' followed by a descriptive noun phrase (issues, latest_event). This uniformity enhances readability and predictability, adhering to a clear convention throughout the tool set.
With only two tools, the server feels under-scoped for a monitoring or error-tracking domain like GlitchTip. Essential operations such as creating, updating, or resolving issues are missing, which limits the server's utility and suggests an incomplete implementation.
The tool set is severely incomplete for error tracking. While it allows reading issues and events, it lacks CRUD operations (e.g., create, update, delete issues) and other key functionalities like searching or filtering, which are critical for comprehensive agent workflows in this domain.