An MCP server for interacting with Sentry via LLMs.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 81%
Response Time: 5h
First Timer Success: 100%
getsentry/sentry-mcp has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in getsentry/sentry-mcp respond to incoming external pull requests in approximately 5.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 69.1 places getsentry/sentry-mcp in the A tier.
The external contributor pull request merge rate for getsentry/sentry-mcp is 81.5%, based on public PR activity from non-core contributors.
getsentry/sentry-mcp does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
An MCP server for interacting with Sentry via LLMs.
Collaborative maintainer environment in getsentry/sentry-mcp. Reviews community pull requests with focus on project quality.
Discussions in getsentry/sentry-mcp focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/getsentry/sentry-mcp?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~26 hours (37% approval). Keep your diff compact for rapid review.
create_project currently requires teamSlug, forcing agents and users to understand Sentry teams before creating a project. Until the upstream API provides a stable implied default, sentry-mcp should infer a sensible team locally while preserving explicit team selection. Current behavior packages/mcp-core/src/tools/catalog/create-project.ts declares teamSlug: ParamTeamSlug and always passes it to apiService.createProject. The tool requires team:read, and every documented example includes a team. This exposes organization structure during headless onboarding even when the caller has no meaningful team preference. User stories As an agent creating a project, I want to omit team and still complete setup. As a user unfamiliar with Sentry teams, I do not want project creation blocked on an organizational concept I did not choose. As a member of a multi-team organization, I still want an explicit teamSlug to win when supplied. Proposed solution Make teamSlug optional in the create_projec
Summary Automated MCP callers need deterministic, closed time windows, but the public input schemas for search_events and search_issues currently expose only the relative period parameter. Please expose optional absolute start and end parameters for both tools. Current behavior search_events already has most of the absolute-time plumbing internally: its embedded-agent output accepts either { statsPeriod } or { start, end } the API client can forward start and end the result formatter can report the exact executed absolute range However, the public tool schema exposes only period. In the structured-query path, an explicitly supplied period is also preferred over the agent's parsed absolute time range. This means a caller cannot make absolute bounds authoritative at the tool boundary. A generic example is a scheduled checkpoint intended to cover exactly: [2026-01-01T00:00:00Z, 2026-01-02T00:00:00Z) The closest public invocation is currently something like: { "organizationSlug": "exa
Summary Our MCP server connector in Claude is missing an icon, making it harder to identify in the integrations list. Details When the Sentry MCP server appears in Claude's connector/integration list, it shows without a branded icon. Other integrations (Amplitude, Asana, Box, Canva, etc.) display their brand icons. Tasks Determine icon requirements (size, format, guidelines) Create/source appropriate Sentry icon asset Submit icon to Anthropic for inclusion
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to getsentry/sentry-mcp, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of getsentry/sentry-mcp acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.5% were successfully merged into the primary branch.
getsentry/sentry-mcp has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 69.1 places getsentry/sentry-mcp in the Welcoming tier.
The external pull request merge rate is 81.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
getsentry/sentry-mcp does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for getsentry/sentry-mcp are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.