Sponsor Slot OpenReach builders tracking 30 Agent SDKs and 226 MCP servers. Book featured placement ($150/wk)
Observability MCPnpmmedium schema drift risk

@sentry/mcp-server

Sentry Official MCP Server by Sentry

Sentry Official MCP Server package.

Live Registry Versionv0.42.0Previous: v0.41.0Published 2026-09-25
Stability Grade
B (81/100)
90-Day Velocity
5 releases
Moderate cadence
Dependencies
5 direct
NPM manifest
License
FSL-1.1-ALv2
Verified on NPM
Recommended Exact Pin: npx -y @sentry/mcp-server@0.42.0
TL;DR Verdict & Quick Citation Summary (2026-10-24)Source: AgentBreakWatch Live NPM Index

Sentry Official MCP Server (@sentry/mcp-server) is currently at v0.42.0 on NPM (published 2026-09-25), with a 90-day stability score of 81/100 (B) and MEDIUM schema drift risk across 5 releases in the past 90 days. v0.42.x consolidates search_issues and get_issue_details parameters, requiring organizationSlug on all multi-org tokens. Production teams should pin npx -y @sentry/mcp-server@0.42.0 rather than using unpinned @latest tags.

Breaking Changes & Tool Schema Drift Analysis

v0.42.x consolidates search_issues and get_issue_details parameters, requiring organizationSlug on all multi-org tokens.

Watched Exports / MCP Tool Signatures:
find_issuesget_issue_detailsanalyze_issue_with_seer
Before (Deprecated / Unpinned Pattern)
{ "name": "get_issue", "arguments": { "issue_id": "PROJ-123" } }
After (Verified v0.42.0 Pattern)
{ "name": "get_issue_details", "arguments": { "organizationSlug": "my-org", "issueId": "PROJ-123" } }

Frequently Asked Questions: @sentry/mcp-server

What is the latest version of @sentry/mcp-server on NPM?

As of 2026-10-24, the latest stable version of @sentry/mcp-server (Sentry Official MCP Server by Sentry) on NPM is v0.42.0, published on 2026-09-25. It has shipped 5 releases in the last 90 days.

Does @sentry/mcp-server v0.42.0 have breaking changes or MCP schema drift risk?

@sentry/mcp-server currently carries a MEDIUM schema drift risk rating with a Stability Score of 81/100 (Grade B). v0.42.x consolidates search_issues and get_issue_details parameters, requiring organizationSlug on all multi-org tokens.

How do I safely pin @sentry/mcp-server in production?

Avoid unpinned @latest tags in production agent configs. Pin the exact verified version using `npx -y @sentry/mcp-server@0.42.0` and monitor find_issues, get_issue_details, analyze_issue_with_seer for parameter or schema changes.

30-Min Registry & Schema Poller

Get Instant Breaking-Change Alerts for @sentry/mcp-server

We poll NPM and getsentry/sentry-mcp every 30 minutes. Get an email with the exact diff when @sentry/mcp-server ships a breaking release beyond v0.42.0.