GlitchTip

This GlitchTip MCP Server lets you connect GlitchTip error monitoring with AI assistants to fetch, analyze, and triage errors. It exposes GlitchTip data to your MCP-enabled clients so you can ask for recent errors, get details on specific issues, and prioritize fixes within your usual AI workflows.

How to use

You enable the GlitchTip MCP Server in your MCP client (such as a CLI, IDE integration, or editor extension) and then run queries against the available tools. Use the server to fetch issues, retrieve the latest events for a specific issue, and prompt the AI to analyze errors, prioritize responses, and suggest fixes. Typical usage includes asking for recent errors, requesting details for a particular issue, or requesting a prioritized list of problems to triage.

How to install

Prerequisites you need before installation include a compatible environment for running MCP servers and access to GlitchTip credentials. You will use a local MCP configuration to register the GlitchTip MCP Server and then run the server via a local command.

GlitchTip MCP Server configuration

{
  "mcpServers": {
    "glitchtip": {
      "command": "npx",
      "args": ["-y", "glitchtip-mcp"],
      "env": {
        "GLITCHTIP_TOKEN": "your-api-token",
        "GLITCHTIP_ORGANIZATION": "your-org-slug",
        "GLITCHTIP_BASE_URL": "https://app.glitchtip.com"
      }
    }
  }
}

Getting Your GlitchTip Credentials

You need credentials to access GlitchTip data. Obtain either an API token or a session ID, plus your organization slug, to configure the MCP server.

Configuration

Set up environment variables for secure access to GlitchTip while using MCP. You can store credentials in a .env file for security and reference them from your MCP config.

Security

Keep credentials secure: do not commit secret values to version control unless you are using a properly protected secrets mechanism. Prefer API tokens for team usage and ensure each developer uses their own credentials.

Troubleshooting

If you encounter authentication or connection issues, verify your token or session ID, confirm your organization slug, and ensure the GLITCHTIP_BASE_URL points to your GlitchTip instance. Check that the MCP server is running and reachable from your development environment.

Usage examples

You can query for recent GlitchTip errors, fetch details for a specific issue, or request a prioritized triage of problems. For example, ask the AI to list recent errors, or to provide a deep dive into a single issue with context and suggested fixes.

Available tools

glitchtip_issues

Fetches issues from GlitchTip. Optional status filter supports 'resolved', 'unresolved', or 'all' (default 'unresolved').

glitchtip_latest_event

Retrieves the latest event for a specific issue with full context, including related data.