Glitchtip MCP Server
Provides complete integration with Glitchtip error tracking platform, enabling management of issues, events, projects, organizations, and teams through the Glitchtip API
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Glitchtip MCP Server show me the latest errors in my-api project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Glitchtip MCP Server
MCP (Model Context Protocol) server for interacting with the Glitchtip API.
Created for internal use mostly by Claude Code. License: GNU AGPLv3
Features
Complete integration with Glitchtip error tracking platform, providing access to:
Issues and error details
Events and error occurrences
Projects and organization management
Teams and member information
Related MCP server: GlitchTip MCP Server
Requirements
Node.js 18+
Glitchtip API token with appropriate scopes (see Authentication section)
Installation
npm installConfiguration
Set the following environment variables:
export GLITCHTIP_API_TOKEN="your-api-token"
export GLITCHTIP_ORGANIZATION_SLUG="your-org-slug"
export GLITCHTIP_API_ENDPOINT="https://app.glitchtip.com" # Or your self-hosted instanceUsage with Claude Desktop
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"glitchtip": {
"command": "npx",
"args": ["-y", "github:CleverMobi/glitchtip-mcp"],
"env": {
"GLITCHTIP_API_TOKEN": "your-api-token",
"GLITCHTIP_ORGANIZATION_SLUG": "your-org-slug",
"GLITCHTIP_API_ENDPOINT": "https://your-glitchtip-instance.com"
}
}
}
}Available Tools
Issue & Event Tools (Require event:read scope)
get_issue
Get complete details of a specific Glitchtip issue including:
Basic issue information (title, status, count, project, etc.)
Latest event details with full stack trace
All comments on the issue
Parameters:
issue_id(required): The ID of the issue to retrieve
Example:
get_issue(issue_id: "21241")Returns a comprehensive object with three sections:
issue: Core issue detailslatestEvent: Most recent occurrence with stack trace, tags, and metadatacomments: Array of all comments with author and timestamp
list_issues
List issues in the organization or a specific project.
Parameters:
project_slug(optional): Filter issues by projectlimit(optional): Maximum number of issues to return (default: 25)
Example:
list_issues(project_slug: "my-project", limit: 10)list_events
List events for a specific project.
Parameters:
project_slug(required): The slug of the projectlimit(optional): Maximum number of events to return (default: 25)
Example:
list_events(project_slug: "my-project", limit: 5)Project & Organization Tools
list_projects
List all Glitchtip projects in the organization.
No parameters required.
Example:
list_projects()get_project
Get details of a specific Glitchtip project.
Parameters:
project_slug(required): The slug of the project to retrieve
Example:
get_project(project_slug: "my-project")get_organization
Get organization details including all projects and teams.
No parameters required.
Example:
get_organization()list_teams
List all teams in the organization.
No parameters required.
Example:
list_teams()Authentication
This server uses Bearer token authentication. Your API token needs specific scopes depending on which tools you want to use:
Required Scopes
Tool | Required Scopes |
|
|
|
|
|
|
|
|
Minimum Token Scopes
For basic project/org information:
project:read,org:read,team:read,member:readFor full functionality including issues:
project:read,org:read,team:read,member:read,event:read
To create an API token in Glitchtip:
Go to your Glitchtip instance
Navigate to Settings → API Tokens
Create a new token with the required scopes
Testing
Test the server functionality:
# Run basic tests
node test-get-issue.jsTroubleshooting
403 Forbidden Errors
If you receive 403 errors when accessing issues or events, your API token is missing the event:read scope. Create a new token with the appropriate scopes.
401 Unauthorized Errors
Ensure your API token is valid and uses Bearer authentication format.
Connection Issues
Verify your GLITCHTIP_API_ENDPOINT is correct and accessible.
Available Tools
7 toolsget_issueA
Get complete details of a specific Glitchtip issue including latest event and comments (requires event:read scope)
Inputs: issue_id (required).
get_organizationC
Get organization details
Inputs: no named parameters.
get_projectB
Get details of a specific Glitchtip project
Inputs: project_slug (required).
list_eventsA
List events for a specific project (requires event:read scope)
Inputs: project_slug (required), limit.
list_issuesB
List issues in the organization or a specific project (requires event:read scope)
Inputs: limit, project_slug.
list_projectsB
List all Glitchtip projects in the organization
Inputs: no named parameters.
list_teamsB
List all teams in the organization
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Let AI agents list, read and resolve Bugsly error-tracking issues and check monitors.
Query your app's logs, metrics and incidents from your AI assistant.
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Production errors and incidents for your agent: stack traces, breadcrumbs, likely causes, triage.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to query, analyze, and resolve errors within the GlitchTip error tracking platform by providing access to issue details and stacktraces. It allows users to list unresolved issues and mark them as fixed using natural language commands.322 PyPI2MIT
- AlicenseBqualityDmaintenanceIntegrates GlitchTip error monitoring with AI assistants to fetch, analyze, and debug production errors. It enables users to list issues, retrieve event details, and perform guided triage of application errors through natural language.2259 npm11MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.MIT
- AlicenseBqualityDmaintenanceIntegrates GlitchTip error monitoring with AI assistants, enabling them to fetch, analyze, and debug issues from your GlitchTip instance.221 npm5MIT