Sentry MCP Server
Official Sentry MCP server that lets AI coding agents pull errors, traces, and performance data from Sentry and manage individual issues.
- Skill Road
- Sentry MCP Server
Categories
Description
The Sentry MCP Server implements the Model Context Protocol and gives AI coding agents access to a Sentry account: search errors and issues and view them in detail with the stack trace, query events and distributed traces, narrow down performance anomalies, inspect releases and projects, and search the Sentry documentation. On top of that there is a small set of write actions — such as resolving, reopening, assigning, or muting an issue, and creating projects, teams, and DSNs. In total the server exposes roughly two dozen tools; the focus is explicitly on developer and debugging workflows rather than full Sentry administration.
Hosted option (recommended)
Sentry runs the server as a hosted remote service at https://mcp.sentry.dev/mcp (HTTP transport). The path can optionally be scoped to an organization (/mcp/{organization}) or a project (/mcp/{organization}/{project}). All connections use OAuth: on the first call the client opens a browser window to sign in to the Sentry account and stores the grant for later sessions. The natural-language search tools (search_events, search_issues) work here without your own key because the service provides the required language model itself.
Local option
Alternatively, the source-available package @sentry/mcp-server (version 0.39.0 at the time of review) can be run locally over stdio:
npx @sentry/mcp-server@latest --access-token=<sentry-user-token>
The token comes from the Sentry account settings and needs the scopes org:read, project:read, project:write, team:read, team:write, and event:write. For the natural-language search tools you additionally need your own access to a language model provider locally (OpenAI, Azure OpenAI, Anthropic, or OpenRouter). Self-hosted Sentry installations are connected via --host=sentry.example.com (and --insecure-http if needed); some features such as Seer are unavailable there and can be turned off with --disable-skills=seer.
For Claude Code there is also a plugin marketplace:
claude plugin marketplace add getsentry/sentry-mcp
claude plugin install sentry-mcp@sentry-mcp
Why the hosted option is preferred
Sentry deliberately built the hosted option so that even the natural-language search tools work without your own language model access: the service runs the required model itself, so users don't need to configure a separate OpenAI or Anthropic key. The local option remains mainly relevant for teams connecting a self-hosted Sentry installation or, for compliance reasons, avoiding routing traffic through an additional third-party service.
Connection, Search and Self-hosting
The hosted server is at https://mcp.sentry.dev and signs in through OAuth. Alternatively, a Sentry token can be passed as a header. Locally you start it over stdio with npx @sentry/mcp-server@latest and an access token in the variable SENTRY_ACCESS_TOKEN. The search tools search_errors, search_traces, search_logs and search_issues translate questions into Sentry's query language. They need an LLM provider for this, namely OpenAI, Azure OpenAI, Anthropic or OpenRouter. Without this configuration only the search tools are unavailable, and everything else keeps working. Self-hosted Sentry instances are connected with the option --host. The seer skill is then excluded by default.
Typical use cases
The server is particularly useful for debugging workflows where a coding agent should ask directly about an error report and evaluate its stack trace with context, without anyone manually switching between the IDE and the Sentry UI. It's also helpful for tracking performance regressions after a deployment or automatically summarizing all open critical issues in a project before a release. Given the limited write scope, the server is less suited for fully administering a Sentry account, such as setting up complex alert rules.
Requirements
A Sentry account with access to the target organization or project. The hosted option only needs an MCP client that supports remote servers over HTTP and OAuth. The local option additionally requires Node.js (npx), a Sentry user token with the right scopes, and — for natural-language search — your own access to a language model provider.
Installation instructions
The Sentry MCP Server can be connected in two ways: as a Sentry-hosted remote service with OAuth sign-in, or as a server run locally over stdio with a Sentry user token. Sentry recommends the hosted option.
Quick start
For the hosted option, register the remote server in your MCP client, e.g. in Claude Code with claude mcp add --transport http sentry https://mcp.sentry.dev/mcp, in Cursor via an mcpServers entry with "url": "https://mcp.sentry.dev/mcp", or in VS Code via a servers entry with "type": "http". On the first call the client opens the OAuth dialog; sign in to the Sentry account there and confirm access. The URL can optionally be scoped to an organization or a project.
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
For the local option, create a token in the Sentry account settings under "User Auth Tokens" with the scopes org:read, project:read, project:write, team:read, team:write, and event:write, and start the server via npx @sentry/mcp-server@latest --access-token=<token>. For natural-language search, additionally set a language model provider's credentials as environment variables. Connect self-hosted Sentry instances via --host=.
npx @sentry/mcp-server@latest --access-token=<token>
Which option fits
The hosted option is the quickest to set up, needs no local process, and includes natural-language error search without your own language model key. The local option makes sense when you need to connect a self-hosted Sentry installation or when MCP traffic must not leave your own network — but then natural-language search requires your own access to OpenAI, Azure OpenAI, Anthropic, or OpenRouter.
Step 1: Connecting the hosted option
Register the remote server in your MCP client. In Claude Code:
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
In Cursor or VS Code, create a server entry with the URL https://mcp.sentry.dev/mcp instead (in VS Code with "type": "http"). On the first call the client opens a browser window for OAuth sign-in to the Sentry account. To keep access narrow from the start, append the organization or project to the URL: https://mcp.sentry.dev/mcp/my-org or https://mcp.sentry.dev/mcp/my-org/my-project.
Step 2: Connecting the local option
In the Sentry account settings under "User Auth Tokens", create a token with the scopes org:read, project:read, project:write, team:read, team:write, and event:write. Then start the server via npx:
npx @sentry/mcp-server@latest --access-token=<token>
For the natural-language search tools, additionally set a language model provider's credentials as environment variables. Connect a self-hosted Sentry installation via --host=sentry.example.com, adding --insecure-http for plain HTTP; turn off unavailable features such as Seer with --disable-skills=seer.
Keeping access tight
The agent sees everything the signed-in account or the token sees in Sentry. For automated workflows, use a dedicated token with as few scopes as possible, treat it like a password, and scope the path to the organization or project you need. Stack traces and events can contain secrets or personal data — when in doubt, check in advance which projects the agent can reach.
Step 3: Verifying the setup
After connecting, test with a harmless task such as "Show me the most recent unresolved errors in project X." Check that only the expected organization and projects appear, and tighten access if needed.
Common connection issues
If no browser window opens for OAuth sign-in on the first call, it may be a blocked pop-up in the client or an environment without a graphical interface — in such cases the client usually displays a URL that can be opened manually in a browser. With the local option, an expired or incorrectly copied token causes authentication errors; a freshly generated token from the account settings usually fixes this.
Switching between the hosted and local options
Anyone starting with the hosted option and later wanting to switch to the local option, for example due to network policy, should fully replace the existing client entry rather than running both in parallel. Two Sentry servers configured simultaneously under different names can otherwise lead to conflicting results if the agent doesn't clearly know which one to address.
Source: the hosted service mcp.sentry.dev and the repository github.com/getsentry/sentry-mcp (README.md, LICENSE.md), plus the npm package @sentry/mcp-server, checked on 2026-09-06.
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Authentication
Hosted option: OAuth sign-in to the Sentry account, triggered from the client; the grant is stored for later sessions. Local option: Sentry user token (--access-token) with the scopes org:read, project:read, project:write, team:read, team:write, event:write; for the HTTP transport alternatively as the header Authorization: Sentry-Bearer <token>.
Required access permissions
Effective access matches the signed-in Sentry account or the token scopes and the optional path scoping to an organization or project. Within that scope, mostly read actions are possible (errors, issues, events, traces, releases, projects, documentation). Only a few write actions are provided: changing issue status and assignment, and creating projects, teams, and DSNs.
Transmitted or stored data
Requests and tool parameters go to the Sentry API. Responses contain the account's monitoring data — including stack traces, event details, and trace data that, depending on the application, may contain personal data or secrets — and are passed to the MCP client and its language model. With the hosted option, the connection runs through Sentry's own service at mcp.sentry.dev, which uses its own language model for natural-language search. With the local option, the server runs on your own machine but still calls the Sentry API and sends search queries to the configured language model provider.
Security risks
Stack traces and event data in Sentry can contain plaintext secrets, tokens, or personal data; through the server these enter the context of the agent and its language model. An overly broad token, or signing in with an account that sees many organizations, widens that radius. Limit access with the path scoping to the organization or project actually needed, use a dedicated token with minimal scopes for automated workflows, treat it like a password, and only deliberately allow the write tools (issue status, project/team/DSN creation).
License and costs
- License
- FSL-1.1-Apache-2.0
- Cost
- free
The MCP server itself is free; the source code is publicly readable (FSL-1.1-Apache-2.0) and converts to Apache-2.0 per version after two years. A Sentry account is required — Sentry offers a free developer tier as well as paid plans, billed independently of the MCP server. With the local option there are additional costs at your chosen language model provider when the natural-language search is used.
Alternatives
Not recorded yet.
At a glance
- Provider
- Sentry
- Status
- Official server
- Deployment
- Local and remote
- Current version
- 0.39.0
- GitHub stars
- 963
- Last reviewed
- 07.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.