How to connect the Sentry MCP server
To connect the official Sentry MCP server, add https://mcp.sentry.dev/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. If your client sends custom headers, you can use a Sentry API token. Sentry documents setup for Claude Code, Cursor and VS Code.
Docs reviewed 5 Nov 2026Not a tested connection.
Try with your key via relay → Sentry blocks requests from other websites, so the explorer uses API Tracker's relay. Anything you enter passes through it and is never stored or logged.
Endpoint https://mcp.sentry.dev/mcp · Registry io.github.getsentry/sentry-mcp 0.42.0
Add Sentry MCP to your client
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Connect Sentry MCP step by step
Before you start
- A Sentry account. The first connection starts an OAuth flow that connects your Sentry account. mcp.sentry.dev
- For a self-hosted Sentry install, Sentry points to the local stdio package rather than the hosted server. github.com/getsentry
Authentication
- Your client → Sentry MCP
- OAuth sign-in, handled by your MCP client. mcp.sentry.devgithub.com/getsentrymodelcontextprotocol.io/specification
- Sentry MCP → Sentry API
- The server acts on your account with the access you approve. github.com/getsentry
Steps
- Open Sentry's MCP setup instructions
- Add the Sentry MCP server to your client
Add https://mcp.sentry.dev/mcp as a remote MCP server that uses the HTTP transport. You can scope the server to an organization or a project by adding the organization slug, or the organization and project slugs, to the path. Sentry recommends project scoping when possible; tools then default to that organization or project.
- Sign in to Sentry and approve access in the OAuth window
- If your client sends custom headers, you can use a Sentry API token
Instead of OAuth, send a Sentry user auth token in the Authorization header using the Sentry-Bearer scheme (not Bearer, which is reserved for MCP OAuth access tokens). The server forwards the token to Sentry and does not store, validate or refresh it. The README lists the scopes org:read, project:read, project:write, team:read, team:write and event:write for a user auth token. Keep the token in an environment variable or secret store.
- List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
What we observed
- 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp, which names the authorization server https://mcp.sentry.dev and scopes org:read, project:write, team:write, event:write and alerts:write.
Sentry MCP questions
What is the Sentry MCP server URL?
The official Sentry MCP server is at https://mcp.sentry.dev/mcp and uses the Streamable HTTP transport.
How do I authenticate with the Sentry MCP server?
Sign in with OAuth when your client prompts you. If your client sends custom headers, you can use a Sentry API token: Instead of OAuth, send a Sentry user auth token in the Authorization header using the Sentry-Bearer scheme (not Bearer, which is reserved for MCP OAuth access tokens). The server forwards the token to Sentry and does not store, validate or refresh it. The README lists the scopes org:read, project:read, project:write, team:read, team:write and event:write for a user auth token. Keep the token in an environment variable or secret store.
Which AI clients can use the Sentry MCP server?
Sentry's documentation covers Claude Code, Cursor and VS Code. Other clients that support remote Streamable HTTP MCP servers may also work.
What do I need before connecting Sentry MCP?
A Sentry account. The first connection starts an OAuth flow that connects your Sentry account. For a self-hosted Sentry install, Sentry points to the local stdio package rather than the hosted server.
Has this Sentry MCP guide been tested?
Sentry's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.
Sources and review
Sentry's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.
Guide source and binding
MCP connection guide (draft 0.1) for io.github.getsentry/sentry-mcp 0.42.0, bound to /remotes/0 of the Registry record by SHA-256 be089a4c2d23….
- mcp.sentry.dev/ · checked 5 Nov 2026
- github.com/getsentry/sentry-mcp · checked 5 Nov 2026
- registry.modelcontextprotocol.io/v0.1/servers/io.github.getsentry%2Fsentry-mcp/versions/0.42.0 · checked 5 Nov 2026
- modelcontextprotocol.io/specification/2026-07-28/basic/authorization · checked 5 Nov 2026