GlitchTip MCP Server

MCP server for integrating GlitchTip error monitoring with AI assistants like Claude.

Installation

Getting Your GlitchTip Credentials

Configuration

*Either GLITCHTIP_TOKEN or GLITCHTIP_SESSION_ID is required

Available Tools

glitchtip_issues

Fetches issues from GlitchTip.

Parameters:

• status (optional): 'resolved', 'unresolved', or 'all' (default: 'unresolved')

Examples:

• “Show me all GlitchTip errors”
• “Get resolved issues”
• “Show all issues including resolved”

glitchtip_latest_event

Gets the latest event for a specific issue with full context.

Parameters:

• issueId: The issue ID

Example: “Get details for issue #123”

Available Resources

glitchtip://issues

Resource endpoint providing all current issues in JSON format.

Available Prompts

recent_errors

Get overview of recent production errors with analysis and prioritization.

Use case: Quick triage of production issues

Example: “Use the recent_errors prompt”

debug_issue

Deep-dive into a specific error with full context and suggested fixes.

Parameters:

• issueId: The issue ID to debug

Use case: Detailed investigation of a specific error

Example: “Use the debug_issue prompt for issue 12345”

Usage Examples

Debug Production Error

User: "Check GlitchTip for recent 500 errors"

AI: I found 3 recent 500 errors:
1. DatabaseConnectionError in /api/users
2. TimeoutError in payment processing
3. ValidationError in checkout flow

User: "Show me details about the payment timeout"

AI: [Analyzes event] The TimeoutError occurs when...
[Provides stack trace and suggested fixes]

Monitor Error Trends

User: "What are the most frequent errors?"

AI: Top errors by frequency:
1. CORS policy errors (145 occurrences)
2. Missing auth token (89 occurrences)
3. Rate limit exceeded (67 occurrences)

Use Prompts for Guided Analysis

User: "Use the recent_errors prompt"

AI: [Analyzes all unresolved issues]
Summary:
- 23 unresolved errors across 5 projects
- Critical: DatabaseConnectionError (89 occurrences)
- High: TimeoutError in payment flow (45 occurrences)
- Medium: ValidationErrors (12 occurrences)

Recommended prioritization:
1. Fix database connection pooling
2. Investigate payment timeout root cause
3. Add validation for edge cases

User: "Use the debug_issue prompt for issue 12345"

AI: [Deep-dives into specific error with stack trace and fix suggestions]

Troubleshooting

Authentication Failed

• Verify your token/session ID is valid
• Check organization slug is correct
• Ensure token has appropriate permissions

Connection Error

• Verify GLITCHTIP_BASE_URL is correct
• Check network connectivity
• Ensure GlitchTip instance is accessible

No Issues Found

• Verify issues exist in GlitchTip
• Check organization slug
• Ensure you have permission to view issues

Security

• Never commit .mcp.json, .cursor/mcp.json, or .env to version control
• Use .env files for storing secrets (automatically ignored by git if added to .gitignore)
• Use API tokens instead of session IDs for team usage
• Each developer should use their own credentials

---

Development & Contributing

Installation

npm install

Build

npm run build

Watch Mode

npm run watch

Test with MCP Inspector

export GLITCHTIP_TOKEN="your-token"
export GLITCHTIP_ORGANIZATION="your-org"
npm run inspector

Project Structure

glitchtip-mcp/
├── src/
│   ├── types.ts      # TypeScript type definitions
│   ├── client.ts     # GlitchTip API client
│   └── index.ts      # MCP server implementation
├── package.json
├── tsconfig.json
└── README.md

License

MIT

---

Based on mcp-glitchtip