Glitchtip MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLITCHTIP_API_TOKEN | Yes | Your Glitchtip API token with appropriate scopes | |
| GLITCHTIP_API_ENDPOINT | No | The Glitchtip API endpoint URL | https://app.glitchtip.com |
| GLITCHTIP_ORGANIZATION_SLUG | Yes | Your 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueA | Get complete details of a specific Glitchtip issue including latest event and comments (requires event:read scope) |
| list_issuesB | List issues in the organization or a specific project (requires event:read scope) |
| list_eventsA | List events for a specific project (requires event:read scope) |
| list_projectsB | List all Glitchtip projects in the organization |
| get_projectB | Get details of a specific Glitchtip project |
| get_organizationC | Get organization details |
| list_teamsB | List all teams in the organization |
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 7 tools
Every tool has a clearly distinct purpose targeting specific resources: get_issue, get_organization, and get_project retrieve single items, while list_events, list_issues, list_projects, and list_teams retrieve collections. No ambiguity exists between tools as each combines a clear action (get/list) with a specific resource type.
All tools follow a consistent verb_noun pattern with snake_case: get_issue, get_organization, get_project, list_events, list_issues, list_projects, list_teams. The naming is perfectly predictable and readable throughout the set.
With 7 tools, the server is well-scoped for monitoring and managing a Glitchtip error-tracking system. Each tool earns its place by covering essential resources (issues, organizations, projects, events, teams) without being overly sparse or bloated.
The toolset provides strong read/list coverage for core Glitchtip entities, enabling monitoring workflows. However, it lacks write operations (e.g., create/update/delete for issues, projects, or teams) and advanced actions like resolving issues, which are typical in error-tracking systems, creating minor gaps that agents might need to work around.