GlitchTip MCP Server
This server lets you list, inspect, and resolve GlitchTip issues through MCP tools.
List issues from the configured GlitchTip project, optionally filtered by status:
unresolved,resolved, orignored(defaultunresolved).Get detailed information for a specific issue by ID, including the full stacktrace and error context.
Mark a specific issue as resolved by ID after fixing the underlying bug.
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 most recent unresolved issues and their stacktraces"
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.
mcp-server-glitchtip
MCP server enabling LLMs to query issues, stacktraces, and resolve errors in GlitchTip.
GlitchTip is an open-source, self-hosted error tracking platform that's API-compatible with Sentry. This MCP server lets AI assistants like Claude directly access your error data to help debug and fix issues faster.
Features
List Issues - Query all unresolved, resolved, or ignored issues
Get Issue Details - Retrieve full stacktraces and error context
Resolve Issues - Mark issues as resolved after fixing them
Related MCP server: Bugsink MCP Server
Installation
Using pip
pip install mcp-server-glitchtipFrom source
git clone https://github.com/hffmnnj/mcp-server-glitchtip.git
cd mcp-server-glitchtip
pip install -e .Configuration
1. Create a GlitchTip API Token
Go to your GlitchTip instance:
https://your-glitchtip.com/profile/auth-tokensClick Create New Token
Copy the token
2. Find Your Organization and Project Slugs
Your organization slug is in the URL when viewing your organization:
https://your-glitchtip.com/organizations/{org-slug}/issuesYour project slug is visible in your project settings or URL:
https://your-glitchtip.com/organizations/{org-slug}/projects/{project-slug}3. Add to Claude Code
claude mcp add mcp-server-glitchtip \
-s user \
-e GLITCHTIP_AUTH_TOKEN=your_token_here \
-e GLITCHTIP_API_URL=https://your-glitchtip.com/api/0/ \
-e GLITCHTIP_ORGANIZATION=your-org-slug \
-e GLITCHTIP_PROJECT=your-project-slug \
-- mcp-server-glitchtip4. Add to Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"glitchtip": {
"command": "mcp-server-glitchtip",
"env": {
"GLITCHTIP_AUTH_TOKEN": "your_token_here",
"GLITCHTIP_API_URL": "https://your-glitchtip.com/api/0/",
"GLITCHTIP_ORGANIZATION": "your-org-slug",
"GLITCHTIP_PROJECT": "your-project-slug"
}
}
}
}Environment Variables
Variable | Required | Description | Example |
| Yes | API token from GlitchTip |
|
| Yes | Base API URL (include trailing slash) |
|
| Yes | Organization slug |
|
| Yes | Project slug |
|
Available Tools
get_glitchtip_issues
List all issues from your GlitchTip project.
Parameters:
status(optional): Filter by status -unresolved,resolved, orignored. Default:unresolved
Example response:
GlitchTip Issues (unresolved):
---
ID: 123 (PROJ-1)
Title: TypeError: Cannot read property 'foo' of undefined
Level: error | Count: 42
Culprit: app.js in handleClick
First: 2024-01-15T10:30:00Z | Last: 2024-01-15T14:22:00Zget_glitchtip_issue
Get detailed information about a specific issue including the full stacktrace.
Parameters:
issue_id(required): The numeric issue ID
resolve_glitchtip_issue
Mark an issue as resolved after fixing the underlying bug.
Parameters:
issue_id(required): The numeric issue ID to resolve
Usage Examples
Once configured, you can ask Claude:
"Show me all unresolved errors in GlitchTip"
"What's the stacktrace for issue 123?"
"What errors are happening most frequently?"
"I fixed that null pointer bug, mark issue 456 as resolved"
Compatibility
This server works with any GlitchTip instance. GlitchTip uses a Sentry-compatible API, so the endpoints follow Sentry's API structure.
Tested with:
GlitchTip 3.x+
Python 3.10+
Development
# Clone the repo
git clone https://github.com/hffmnnj/mcp-server-glitchtip.git
cd mcp-server-glitchtip
# Create virtual environment
python -m venv venv
source venv/bin/activate # or `venv\Scripts\activate` on Windows
# Install in development mode
pip install -e .
# Run the server locally
GLITCHTIP_AUTH_TOKEN=xxx \
GLITCHTIP_API_URL=https://your-glitchtip.com/api/0/ \
GLITCHTIP_ORGANIZATION=your-org \
GLITCHTIP_PROJECT=your-project \
mcp-server-glitchtipRelated Projects
GlitchTip - Open source error tracking
MCP - Model Context Protocol
mcp-sentry - Similar MCP server for Sentry.io
License
MIT License - see LICENSE for details.
Available Tools
3 toolsget_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.
Inputs: issue_id (required).
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.
Inputs: status.
resolve_glitchtip_issueA
Mark a GlitchTip issue as resolved after fixing it. Use this after you've fixed the bug causing the error.
Inputs: issue_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
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.
Issue tracking for software projects: issues, epics, releases, docs and boards, from your AI.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables interaction with Glitchtip error tracking platform through natural language. Provides access to issues, events, projects, teams, and organization management for comprehensive error monitoring and debugging.718 npm3AGPL 3.0
- AlicenseBqualityDmaintenanceEnables AI assistants to query and analyze errors from Bugsink self-hosted error tracking instances. Supports listing projects, teams, issues, and viewing detailed error events with stacktraces.16113 npm19MIT
- 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
- AlicenseBqualityDmaintenanceIntegrates GlitchTip error monitoring with AI assistants, enabling them to fetch, analyze, and debug issues from your GlitchTip instance.221 npm5MIT