GlitchTip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLITCHTIP_API_URL | Yes | Base API URL (include trailing slash). Example: https://glitchtip.example.com/api/0/ | |
| GLITCHTIP_PROJECT | Yes | Project slug | |
| GLITCHTIP_AUTH_TOKEN | Yes | API token from GlitchTip | |
| GLITCHTIP_ORGANIZATION | Yes | 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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_glitchtip_issuesA | List all issues from GlitchTip for the configured project. Use this to see all current errors and exceptions in production. Returns issue titles, counts, status, and when they were first/last seen. |
| get_glitchtip_issueA | Get detailed information about a specific GlitchTip issue including full stacktrace. Use this when you need to investigate a specific error in detail. Provides the complete stacktrace, error counts, and timing information. |
| resolve_glitchtip_issueA | Mark a GlitchTip issue as resolved after fixing it. Use this after you've fixed the bug causing the error. |
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 3 tools
Each tool has a clearly distinct purpose: get_glitchtip_issue retrieves detailed information about a single issue, get_glitchtip_issues lists all issues, and resolve_glitchtip_issue marks an issue as resolved. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern with 'glitchtip_issue' as the common noun component. The verbs 'get', 'get' (for list), and 'resolve' are clear and uniformly applied in snake_case, providing a predictable naming convention throughout.
With only 3 tools, the set feels thin for a GlitchTip server, which might be expected to handle more operations like creating issues, updating them, or managing projects. While the tools cover basic viewing and resolving, the count is borderline for comprehensive error management.
The tool set has significant gaps for a GlitchTip server. It lacks create, update, or delete operations for issues, and there are no tools for managing projects, users, or other GlitchTip entities. This incomplete surface will likely cause agent failures when trying to perform common error management tasks beyond viewing and resolving.