Why you'd want it
Sentry runs a remote MCP server at mcp.sentry.dev that uses OAuth and acts as middleware to the Sentry API, with tools chosen for debugging workflows in coding assistants rather than full Sentry coverage. You can scope the connection to one organization or project, which sets defaults and hides discovery tools. For self-hosted Sentry there is a stdio transport (npx @sentry/mcp-server) that takes a user auth token; its AI-powered search tools need an OpenAI, Azure OpenAI, Anthropic or OpenRouter key.
Best for
- Teams already on Sentry
- Debugging production errors from the editor
- Self-hosted Sentry via the stdio transport
Use it when
Your app reports to Sentry and you want the coding agent to pull issue details, errors and traces while it works on a fix.
Skip it if
You do not use Sentry. Sentry says it is not a general-purpose server for all Sentry functionality, and the stdio transport is still a work in progress.
Editor's note
The Sentry MCP server now lives in getsentry/toolkit alongside the Sentry CLI.