Sentry MCP Server

Official

Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.

Local + remotestdiostreamable-httpTypeScriptMIT★ 400

What is the Sentry MCP Server?

Sentry’s MCP integration connects a supported assistant to error and project context for investigation workflows.

Trace a specific incident

Supply the issue link, project and relevant release. Ask for the recurring failure, affected paths and evidence from the available event context. Distinguish what the events show from a hypothesis about the code.

Connection and scope

Use the current Sentry documentation for the hosted endpoint, client connection and account authorization. Confirm that the account can reach the intended organization and project. Available workflows depend on the connected service and tool set.

Review the resulting workflow

A diagnosis should end in a checkable action: a reproduction, a proposed patch or a monitoring query. Run the application tests and observe subsequent events before declaring the incident fixed. Closing an issue alone does not correct the underlying code.

Publisher documentation

Source 1

What you can do with it

Debug from a link

Paste a Sentry issue URL and get the full-context investigation.

Release health checks

"What broke since we shipped?" answered from real error data.

Root-cause on demand

Seer analysis plus your repo-connected assistant closes error-to-fix.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
find_issues / get_issue_detailsQuery issues and read full event context
find_projects / find_releasesProject and release enumeration
get_event_attachmentFetch event attachments
update_issueResolve, assign and manage issues
begin_seer_issue_fix / get_seer_issue_fix_statusInvoke Sentry's Seer root-cause agent
create_dsn / find_dsnsManage project DSNs

How to install the Sentry MCP Server

claude mcp add --transport http sentry https://mcp.sentry.dev/mcp

Configuration

A Sentry account (SaaS or self-hosted). OAuth for the hosted server; a user auth token for local mode.

VariableDescriptionRequired
SENTRY_ACCESS_TOKENUser auth token for local mode (remote uses OAuth)Optional
SENTRY_HOSTSelf-hosted Sentry hostname if applicableOptional

Example prompts to try

  • “Investigate this Sentry issue and propose a fix: [issue URL]”
  • “Which production issues affected the most users this week?”
  • “Run Seer on the checkout NullPointerException and summarise its analysis.”

Frequently asked questions

Yes — the hosted MCP server supports both SaaS and self-hosted backends, and local mode can point at your instance via SENTRY_HOST.