This is an early release preview. You may encounter bugs.
Sentry MCP logo
Unclaimed

Tool monitoring coding

Sentry MCP

MCP server giving coding agents access to Sentry issues and traces.

A 84/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About Sentry MCP.

Sentry MCP is a Model Context Protocol server that connects coding agents to Sentry, so an agent can search errors, analyze performance, triage issues, read Sentry documentation, and manage projects. It targets human-in-the-loop coding agents such as Cursor and Claude Code, and its tool selection centers on developer workflows and debugging rather than covering all Sentry functionality.

The main deployment is a hosted remote server that acts as middleware in front of the Sentry API, built on Cloudflare's remote MCP work. Connections authenticate with OAuth, and a connection can be scoped to one organization or project, which defaults tools to that scope and hides unnecessary discovery tools. Clients that send custom headers can instead pass a Sentry API token directly. A stdio transport runs the server against self-hosted Sentry.

Tools are grouped into skills (such as inspect, triage, project management, and Seer) that can be granted or disabled per connection. The AI-powered search tools translate natural-language queries into Sentry's query syntax using an LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter), and the remaining tools work without one. A Claude Code plugin adds a subagent that Claude delegates to for questions about Sentry errors, issues, traces, or performance. The same repository also contains the Sentry CLI.

  • Remote MCP server: a hosted HTTP endpoint with OAuth sign-in to your Sentry account
  • Organization and project scoping: scoped connections default tools to one org or project and hide discovery tools
  • Natural-language search: AI-powered tools translate questions into Sentry queries over errors, traces, logs, and issues
  • Skill-based tool sets: grant or disable skills such as inspect, triage, project management, and Seer per connection
  • Self-hosted Sentry: a stdio transport for self-hosted installs, with Seer left out by default
  • Direct token auth: remote clients can forward a Sentry API token in a header instead of using OAuth
  • Claude Code plugin: a subagent that Claude delegates to for Sentry errors, issues, traces, and performance
  • Experimental variants: an opt-in mode for forward-looking tool variants and features

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with Sentry MCP.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get Sentry MCP →

Browse the catalog