Sentry Official Remote MCP Server
Sentry's remote MCP (mcp.sentry.dev) brings error context into your agent: fetch issue details, stack traces and event searches, and resolve issues without leaving the conversation.
- Provider
- Sentry โ
- Source
- https://github.com/getsentry/sentry-mcp โ
- Categories
- โ๏ธ Cloud, Infrastructure & DevOps๐ ๏ธ Developer Tools & Git
ไธญๆ็ฎไป
Sentry ๆ็ฎก็่ฟ็จ MCP ๆๅกๅจใAI ไปฃ็ๅฏไปฅ็ดๆฅๅจ IDE ไธญๆฅ็้่ฏฏ Issueใๆ็ดขไบไปถๅนถๅค็ๅๅฝ้ฎ้ขใ
Legacy SSE endpoint
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"sentry": {
"url": "https://mcp.sentry.dev/mcp"
}
}
}claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Or add to .vscode/mcp.json:
{
"servers": {
"sentry": {
"type": "http",
"url": "https://mcp.sentry.dev/mcp"
}
}
}- Open Settings โ Connectors (Integrations) โ Add Custom Connector.
- Paste the endpoint URL:
https://mcp.sentry.dev/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"sentry": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.sentry.dev/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"sentry": {
"serverUrl": "https://mcp.sentry.dev/mcp"
}
}
}๐งฐ Tools exposed by Sentry MCP (4)
| Tool | Safety | Description | Parameters |
|---|---|---|---|
| get_sentry_issue | ๐ข Read | Fetch details and stack traces for a Sentry issue. | issueId*: stringorganizationSlug: string |
| list_organization_projects | ๐ข Read | List projects in a Sentry organization. | organizationSlug: string |
| search_events | ๐ข Read | Search Sentry events with Discover-style queries. | query*: stringprojectSlug: stringorganizationSlug: string |
| resolve_issue | ๐ Write | Mark a Sentry issue as resolved. This changes issue state in Sentry. | issueId*: stringorganizationSlug: string |
๐ OAuth 2.1 & Security
- Auth type
- OAuth 2.1
- Dynamic Client Registration
- โ Supported
- PKCE S256
- โ Supported
- Scopes
org:readproject:readevent:readevent:write- Protected resource metadata
- https://mcp.sentry.dev/.well-known/oauth-protected-resource (expected location)
๐งฉ Recommended Agent Skills
๐ Guide
Sentry MCP โ Remote MCP Server
Sentry's hosted MCP gives agents access to your organization's error data: issue details, event search and project listings. It is fully open source (getsentry/sentry-mcp) and implements OAuth 2.1 so each user connects their own Sentry account โ the agent only sees projects you can see. Both /mcp (Streamable HTTP) and /sse (legacy) transports are available.
Endpoint & Transport
- Endpoint URL:
https://mcp.sentry.dev/mcp - Legacy SSE endpoint:
https://mcp.sentry.dev/sse - Transport: Streamable HTTP + legacy SSE
Authentication
Sentry MCP uses OAuth 2.1 โ the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow โ PKCE and Dynamic Client Registration, so no manual client setup is needed โ and simply open a browser consent screen.
Available Tools (4)
| Tool | Safety | Description |
|---|---|---|
get_sentry_issue |
read | Fetch details and stack traces for a Sentry issue. |
list_organization_projects |
read | List projects in a Sentry organization. |
search_events |
read | Search Sentry events with Discover-style queries. |
resolve_issue |
write | Mark a Sentry issue as resolved. This changes issue state in Sentry. |
Connect in 30 Seconds
Claude Code โ one command:
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp
Cursor โ add to ~/.cursor/mcp.json:
{ "mcpServers": { "sentry": { "url": "https://mcp.sentry.dev/mcp" } } }
VS Code โ add to .vscode/mcp.json:
{ "servers": { "sentry": { "type": "http", "url": "https://mcp.sentry.dev/mcp" } } }
Claude Desktop & stdio clients โ bridge with mcp-remote:
{ "mcpServers": { "sentry": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.sentry.dev/mcp"] } } }
On first connect your client opens a browser OAuth consent screen โ approve it and tools become available immediately.
Troubleshooting
- 401 Unauthorized on connect โ that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact
WWW-Authenticatechallenge. - Which URL should I use? Prefer
https://mcp.sentry.dev/mcp(Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec. - "Session expired" / stale
Mcp-Session-Idโ just re-sendinitialize; stateless clients can ignore session headers entirely. - The OAuth flow maps to your Sentry user permissions; self-hosted Sentry instances are not covered by this hosted endpoint.
- Prefer /mcp for new setups; /sse remains for legacy clients.
๐ How to Connect
- Copy the Sentry MCP endpoint URLThe remote endpoint is https://mcp.sentry.dev/mcp. A legacy SSE endpoint is also available at https://mcp.sentry.dev/sse.
- Add it to your MCP clientClaude Code:
claude mcp add --transport http sentry https://mcp.sentry.dev/mcp. Cursor: add"sentry": { "url": "https://mcp.sentry.dev/mcp" }undermcpServersin ~/.cursor/mcp.json. Other clients work similarly. - Complete the OAuth consentOn first connection your client opens a Sentry consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
- Verify with the online inspectorPaste https://mcp.sentry.dev/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Sentry MCP's 4 tools respond.
โ FAQ
What is the Sentry MCP remote MCP endpoint?
The primary endpoint is https://mcp.sentry.dev/mcp, with a legacy SSE endpoint at https://mcp.sentry.dev/sse. It is an official first-party server operated by Sentry, speaking the Streamable HTTP + legacy SSE transport.
Should I use Sentry MCP's /mcp or /sse endpoint?
Use https://mcp.sentry.dev/mcp โ Streamable HTTP is the current MCP transport and what every modern client defaults to. https://mcp.sentry.dev/sse exists only for clients still on the legacy HTTP+SSE transport from the 2024 spec.
How do I authenticate with Sentry MCP?
Sentry MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.
I'm getting a 401 Unauthorized from Sentry MCP โ what's wrong?
A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.
Which MCP clients work with Sentry MCP?
Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http sentry https://mcp.sentry.dev/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.
What tools does Sentry MCP expose?
4 tools are cataloged in this directory โ including `get_sentry_issue`, `list_organization_projects`, `search_events` and more. Use our online inspector to fetch the live tool list straight from the endpoint.
๐ Connect Guides
๐ Embed Status Badge in README
Related Servers
Cloudflare's free, authless documentation MCP server. Agents can search the full Cloudflare docs corpus โ no account or token required.
Vercel's official remote MCP server. Agents can list deployments, fetch build logs and search Vercel docs with a token-authorized connection.
Cloudflare's authenticated MCP server for account bindings. Agents can list Workers, query D1 databases, and inspect KV and R2 namespaces.
Cloudflare's authenticated observability MCP server. Query Worker logs, trace events and error analytics from any MCP client.