MCP GlitchTip
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLITCHTIP_TOKEN | No | Your GlitchTip API token (recommended) | |
| GLITCHTIP_BASE_URL | No | GlitchTip instance URL | https://app.glitchtip.com |
| GLITCHTIP_SESSION_ID | No | Your GlitchTip session cookie | |
| GLITCHTIP_ORGANIZATION | Yes | Organization slug from GlitchTip URL |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glitchtip_issuesB | 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 |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GlitchTip Issues | All issues from GlitchTip error monitoring |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one lists all issues, the other retrieves the latest event for a specific issue. No overlap.
Both tools follow a consistent snake_case pattern with the 'glitchtip_' prefix and a clear noun phrase.
With only 2 tools, the server is minimal. While not extreme, it feels thin for a typical issue-tracking domain.
Only read operations are available (list issues, get latest event). Missing create, update, delete, and other event retrieval, leaving significant gaps.