No Hype, Just Context: Using GlitchTip's MCP server to debug GlitchTip

You'll notice there are no AI bots hanging around when you use GlitchTip. We never sell your data to anyone, nor do we use it to train models. And we make it very easy to run GlitchTip yourself.

What happens when you do want to pull in your GlitchTip data into your preferred AI solution? GlitchTip has a built-in Model Context Protocol (MCP) server to make this easy.

You can use MCP in tools like Claude Code, Zed and many others. Add the MCP server at https://app.glitchtip.com/mcp (update the domain to match your instance). It will prompt an OAuth connection that you'll need to approve. And that's it. Ask the agent to perform a task such as triaging bugs, finding slow SQL queries, etc.

No copying and pasting GlitchTip to an AI here. But Claude probably should have sorted by -priority. It could have been noticed that the high-volume error stopped a while ago, indicating that I am lazy at resolving my own company’s GlitchTip issues. The shoemaker's children go barefoot.

We aren't pivoting to an AI company, you can’t even buy AI from us. This tiny MCP extension does not cost extra. And we aren't using VC money to lock you into a proprietary ecosystem. GlitchTip remains OSI-approved free software, funded by our users. If you want to give your LLM direct access to your production errors, the MCP server is available today. It's already running on our hosted platform, or you can enable it on your own instance by setting GLITCHTIP_ENABLE_MCP=true. Check out the docs to get connected, and let us know what you break (and fix).