GlitchTip MCP Server

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

Installation

Prerequisites

1. Cursor IDE installed

2. GlitchTip API token or session ID

3. Your GlitchTip organization slug

Quick Install

Click the button above and follow the installation flow, or manually configure:

Manual Configuration

1. Open your MCP configuration file:

   • Global (all projects): ~/.cursor/mcp.json

   • Project-specific: .cursor/mcp.json in project root

2. Add the following configuration:

3. Replace the environment variables with your actual values

4. Save the file and restart Cursor

Using .env File (Recommended)

For better security, store credentials in a .env file:

1. Create .env in your project root:

2. Update .cursor/mcp.json:

3. Add .env to .gitignore:

Verify Installation

1. Restart Cursor completely

2. Check for green dot in Settings → Tools & Integrations → MCP Tools

3. In chat/composer, check "Available Tools"

4. Test with: "Show me GlitchTip errors"

Prerequisites

1. Claude Desktop installed

2. GlitchTip API token or session ID

3. Your GlitchTip organization slug

Configuration

1. Open your Claude Desktop configuration file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

   • Windows: %APPDATA%\Claude\claude_desktop_config.json

   • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add the following configuration:

3. Replace the environment variables with your actual values

4. Save the file and restart Claude Desktop

Using .env File (Recommended)

For better security, store credentials in a .env file:

1. Create .env in your project root:

2. Update claude_desktop_config.json:

3. Add .env to .gitignore:

Verify Installation

1. Restart Claude Desktop completely

2. Look for the 🔌 icon in the bottom right

3. Click it to see available MCP servers

4. Test with: "Show me GlitchTip errors"

Prerequisites

1. Claude Code CLI installed

2. GlitchTip API token or session ID

3. Your GlitchTip organization slug

Installation

Run the following command in your terminal:

Using Environment Variables (Recommended)

For better security, store credentials in a .env file:

1. Create .env in your project root:

2. Add the MCP server:

3. Add .env to .gitignore:

Configuration Scopes

• -s user: Available across all projects

• -s project: Shared via .mcp.json file (committed to repo)

• Default: local (current project only)

Verify Installation

Test with: "Show me GlitchTip errors"

Prerequisites

1. VS Code installed

2. Cline extension installed

3. GlitchTip API token or session ID

4. Your GlitchTip organization slug

Configuration

1. Open VS Code

2. Click the MCP Servers icon (📚) in the Cline extension

3. Click the "Installed" tab

4. Click "Configure MCP Servers"

5. Add the following to cline_mcp_settings.json:

6. Replace the environment variables with your actual values

7. Save the file

8. Restart VS Code or reload the Cline extension

Using .env File (Recommended)

For better security, store credentials in a .env file:

1. Create .env in your project root:

2. Update cline_mcp_settings.json:

3. Add .env to .gitignore:

Verify Installation

1. Restart VS Code or reload Cline

2. Check the MCP Servers panel in Cline

3. Look for "glitchtip" in the list of connected servers

4. Test with: "Show me GlitchTip errors"

Getting Your GlitchTip Credentials

1. Log in to GlitchTip

2. Go to https://app.glitchtip.com/profile/auth-tokens

3. Create a new API token

4. Copy the token

1. Log in to GlitchTip

2. Open browser DevTools (F12)

3. Go to Application/Storage → Cookies

4. Copy the sessionid cookie value

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

Monitor Error Trends

Use Prompts for Guided Analysis

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

Build

Watch Mode

Test with MCP Inspector

Project Structure

License

MIT

Based on mcp-glitchtip