--- title: "Sentry (sentry.io) MCP server | Agent MCP Directory" description: "Sentry (sentry.io): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list." canonical: https://agentmcpdirectory.com/directory/sentry-io site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Sentry (sentry.io) MCP server | Agent MCP Directory > Sentry (sentry.io): sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Endpoint, auth type and tool list. Source: https://agentmcpdirectory.com/directory/sentry-io Site: Agent MCP Directory Last reviewed: 2026-11-05 # Sentry: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sentry at mcp.sentry.dev answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Sentry | | --- | --- | | Domain | sentry.io | | Category | Infrastructure (Ora leaderboard category) | | MCP server | Sign-in required (OAuth with client registration) | | Tranco rank | 102 on the list of 4 November 2026 | | Ora score | 79, grade B; Ora scanned the domain on 31 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sentry.io, a vendor-published score) | | Company found through | the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.sentry.dev/mcp | | --- | --- | | How it was found | listed in the vendor's own documentation; the awesome-remote-mcp-servers list; Ora's public leaderboard; the shared crawl, which found /.well-known/mcp.json on the domain | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:01 UTC | | Handshake time | 246 ms over 1 attempt | | Documentation | docs.sentry.io | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:55:51Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 117 ms - 20:01:26Z https://mcp.sentry.dev/mcp sent initialize result auth-required (HTTP 401) 246 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp" | | Protected resource metadata | mcp.sentry.dev | | Authorization server metadata | mcp.sentry.dev | | Registration endpoint | https://mcp.sentry.dev/oauth/register | | Client ID metadata documents | supported | | Auth as listed by a registry | OAuth2.1 (a claim, not checked by connecting) | ### The sign-in route, step by step 1. Request `https://mcp.sentry.dev/mcp` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.sentry.dev/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI | Package | @sentry/cli on npm (page) | | --- | --- | | Exists | yes | | Latest version | 3.8.2 | | Last publish | 22 October 2026 | | Command names | sentry-cli | | Checked | 4 November 2026 | ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not detected on the home page by the shared crawl. | | MCP discovery file | Found: sentry.io/.well-known/mcp.json answered with a valid document in the shared crawl. | | A2A agent card | The path answered with a web page, not the file. Not counted. | | A2A agent card (older path) | The path answered with a web page, not the file. Not counted. | | agents.json | The path answered with a web page, not the file. Not counted. | | OAuth authorization server metadata | Found: sentry.io/.well-known/oauth-authorization-server answered with a valid document in the shared crawl. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | No | | GitHub MCP Registry | No | | awesome-remote-mcp-servers | Yes | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/sentry-io/index.md) ## Sources - [Sentry MCP documentation](https://docs.sentry.io/product/sentry-mcp/), read 4 November 2026 - [Ora score page for sentry.io](https://ora.ai/score/sentry.io?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 31 October 2026, read from GET /api/score) - [Sentry website](https://sentry.io), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026