Sentry MCP Server

Official Sentry MCP server for accessing issues, events, traces, releases, DSNs, and Seer AI root-cause analysis from AI coding assistants.

Developer Tools by Sentry OAuth2 active

Connect (Remote Server) GitHub Docs npm: @sentry/mcp-server

Overview

The Sentry MCP server is the official Model Context Protocol integration maintained by Sentry. It gives AI coding agents direct access to a Sentry organization's issues, events, traces, releases, projects, teams, and DSNs, plus the ability to trigger Seer, Sentry's AI-powered root cause analysis. The server is offered as a hosted remote endpoint at https://mcp.sentry.dev/mcp with OAuth, and as a local stdio binary (@sentry/mcp-server) for self-hosted Sentry installs or scoped local use.

It exposes roughly 25 tools split across read operations (search and inspect issues, events, traces, docs) and a small set of write operations (update issue status or assignment, create projects, teams, and DSNs). Natural language search tools like search_issues and search_events translate plain English into Sentry query syntax, while analyze_issue_with_seer runs Seer for root-cause and fix suggestions.

The server is production-ready and works with Claude Code, Cursor, Claude Desktop, VS Code/Copilot, Codex, Windsurf, Warp, and other MCP-capable clients. Tool groups can be selectively exposed at auth time to keep the context window focused.

Tools

Tool	Description
`find_organizations`	Find Sentry organizations the authenticated user has access to.
`find_projects`	Find projects in a Sentry organization, with optional name or slug filter.
`find_teams`	Find teams within a Sentry organization.
`find_releases`	Find releases in a Sentry organization.
`find_dsns`	List all Sentry DSNs for a project.
`search_issues`	Search for grouped issues in Sentry using natural language that is translated into Sentry query syntax.
`search_events`	Search events with counts and aggregations using natural language.
`search_issue_events`	Search and filter events within a specific issue.
`list_issues`	List issues in an organization using Sentry query syntax.
`list_events`	Search events using Sentry query syntax.
`list_issue_events`	List events within a specific issue.
`get_issue_details`	Get detailed information about a specific issue, including stack trace, file locations, and context.
`get_issue_tag_values`	Get tag value distribution for an issue.
`get_event_attachment`	Download attachments from a Sentry event.
`get_trace_details`	Get detailed information about a distributed trace.
`get_sentry_resource`	Fetch a Sentry resource by URL or by type and ID.
`search_docs`	Search the Sentry documentation.
`get_doc`	Fetch markdown content of a Sentry docs page.
`whoami`	Identify the authenticated Sentry user.
`analyze_issue_with_seer`	Run Seer AI root cause analysis on a production issue, returning file locations, explanations, and code fix suggestions.
`update_issue`	Update an issue's status or assignment.
`create_project`	Create a new project in Sentry.
`create_team`	Create a new team in a Sentry organization.
`create_dsn`	Create an additional DSN for a project.
`update_project`	Update project settings in Sentry.

Setup Guide

Option 1: Hosted server (recommended)

Point your MCP client at the hosted endpoint. Sign in via OAuth in the browser the first time you connect.

{
  "mcpServers": {
    "sentry": {
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}

For one-step install in a supported client:

npx add-mcp https://mcp.sentry.dev/mcp

Option 2: Local stdio transport

Useful for self-hosted Sentry or scoping the server to a single org. Tokens cache at ~/.sentry/mcp.json.

npx @sentry/mcp-server@latest

{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": ["@sentry/mcp-server@latest", "--organization-slug=my-org"]
    }
  }
}

Option 3: Self-hosted Sentry

Pass a user auth token and your Sentry host:

npx @sentry/mcp-server@latest --access-token=YOUR_TOKEN --host=sentry.example.com

Required token scopes: org:read, project:read, project:write, team:read, team:write, event:write.

Prerequisites

A Sentry account (cloud or self-hosted)
An MCP-capable client (Claude Code, Cursor, Claude Desktop, VS Code/Copilot, Windsurf, Codex, Warp, etc.)
For AI-powered search tools (search_issues, search_events) over stdio: an OPENAI_API_KEY env var
Seer analysis is cloud-only and not available on self-hosted Sentry

Use Cases

Triage a Sentry issue inline in your IDE: pull the stack trace, identify the failing file and line, and ask the agent to draft a fix
Run Seer root-cause analysis on a production error and apply the suggested code change without leaving Cursor or Claude Code
Query "top unresolved errors in production in the last 24 hours" or "errors spiking after release 2.4.0" using natural language
Bootstrap a new service by creating a Sentry project, team, and DSN, then wire the DSN into your app config
Update issue status (resolve, ignore) or assign issues to teammates during code review or incident response

Example Prompts

"Show me the top unresolved issues in the web project from the last 7 days and summarize the most impactful one."
"Run Seer on issue PROJ-1234 and apply the suggested fix to my current branch."
"Search for TypeError events in production for release 4.2.0 and group them by browser."
"Create a new Sentry project called payments-api under the platform team and give me the DSN."
"Resolve issue PROJ-9876 and assign issue PROJ-9877 to @alice."

Pros

Official, maintained by Sentry, with both hosted (OAuth) and local stdio transports
Broad coverage: roughly 25 tools spanning issues, events, traces, releases, DSNs, teams, projects, and docs
Natural language search via search_issues and search_events plus Seer AI root cause analysis
Selectable tool groups at auth time to keep context windows small

Limitations

Seer analysis is cloud-only and unavailable on self-hosted Sentry
AI-powered search tools require an external LLM provider key (e.g. OPENAI_API_KEY) when running over stdio
Sentry notes the server is production-ready but the underlying MCP spec is still evolving, so behavior may change

Alternatives

Datadog MCP server for APM and log monitoring workflows
Raygun or Rollbar community MCP integrations for error tracking
Self-built integration against the Sentry REST API for read-only dashboards or custom write flows