Sentry MCP Server
Sentry MCP Server is an MCP server published by Sentry, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Sentry. Last verified 2026-08-20.
Does Sentry MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. Sentry MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is Sentry MCP Server a first-party (official) MCP server?
Yes. Sentry MCP Server is the first-party MCP server published by Sentry (last verified 2026-08-20).
How do I connect to Sentry MCP Server?
Sentry MCP Server is available via a hosted remote endpoint at https://mcp.sentry.dev/mcp, the package npm:@sentry/mcp-server, the official MCP Registry under io.github.getsentry/sentry-mcp, the source repository at https://github.com/getsentry/sentry-mcp. Authentication: oauth. Transports: streamable-http, stdio.
Does Sentry MCP Server support MCP revision 2026-07-28?
No. Sentry MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
Does Sentry MCP Server support MCP revision 2025-11-25?
Yes. Sentry MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).
When were Sentry MCP Server's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
The Sentry MCP Server is Sentry's first-party server for its error
monitoring and issue-tracking data. The README frames it as middleware
to the upstream Sentry API, aimed at coding assistants, and built on
Cloudflare's remote-MCP pattern. The primary deployment is hosted at
https://mcp.sentry.dev; a local stdio transport is documented as a
work in progress for self-hosted Sentry installs, authorized with a
Sentry user auth token.
Authorization on the hosted endpoint is OAuth, confirmed first-hand: a
2026-08-07 probe of https://mcp.sentry.dev/mcp returned HTTP 401 with
a Bearer challenge and an RFC 9728 resource_metadata URL. The capability
set is not observable without credentials.
Authority is verifiable from the GitHub-verified getsentry organization
and the repository's own homepage field pointing at mcp.sentry.dev. No
surface names a supported MCP specification revision; spec_status is
unknown. The official MCP Registry record describes 0.25.0 from
December 2025, while npm's latest is 0.37.0.
Which MCP spec revisions does Sentry MCP Server support?
Sentry MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Not supported | Source | |
| MCP 2025-11-25 | Supported | Source |
How widely adopted is Sentry MCP Server?
Ranked #18 in The MCP 500 with Adoption Index 68.09 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 83,341 | API · |
| GitHub stars | 853 | API · |
| GitHub forks | 144 | API · |
| Last push | 2026-09-14T19:43:44Z | API · |
| Repository archived | no | API · |
Repository and package signals for Sentry MCP Server
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 102
- Primary language
- TypeScript
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: mcp-server, tag-production — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.37.0- Last published
- First published
- Releases
- 42
- License (package)
- FSL-1.1-ALv2
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 10.7 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record io.github.getsentry/sentry-mcp version 0.25.0 (published 2025-12-17) - npm package @sentry/mcp-server, stdio transport; npm's latest is 0.37.0, ahead of the record - accessed
- getsentry/sentry-mcp README - "This remote MCP server acts as middleware to the upstream Sentry API, optimized for coding assistants"; hosted at https://mcp.sentry.dev, based on Cloudflare's remote-MCP work; a stdio transport is documented as a work in progress needing a Sentry user auth token for self-hosted installs; homepage field mcp.sentry.dev - accessed
- Endpoint probe of https://mcp.sentry.dev/mcp - HTTP 401 with a Bearer WWW-Authenticate challenge carrying realm="OAuth" and an RFC 9728 resource_metadata URL; OAuth requirement confirmed first-hand, capability set not observable without credentials - accessed
- Staleness re-verification 2026-08-18 - endpoint probe of https://mcp.sentry.dev/mcp returned HTTP 401 with WWW-Authenticate: Bearer realm="OAuth", error="invalid_token", re-confirming the OAuth requirement first-hand; the capability set is not observable without credentials - accessed
- npm registry metadata for @sentry/mcp-server at published version 0.37.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed