$ loading_
Access Sentry data to investigate errors, events, releases, and project health.
This is an open-source MCP server for accessing Sentry. Its main security considerations are the required Sentry credentials and communication with the configured Sentry service. Given its official registry presence, auditable source code, and recent maintenance, it appears to be a typical caution-level tool with no clear high-risk red flags in the provided material.
It requires SENTRY_AUTH_TOKEN and SENTRY_BASE_URL; the auth token is a sensitive credential, and leakage could enable unauthorized access to or actions on Sentry projects, issues, events, or releases. The material does not show unusual privilege requests or explicit credential misuse patterns, but the token should be handled as highly sensitive.
Although no fixed remote host is listed, the presence of SENTRY_BASE_URL and the stated functionality indicate it will connect to the user-configured Sentry service/API and may transmit data related to error tracking, issues, events, releases, and projects. This is normal network egress for its declared purpose, with no evidence of exfiltration to unrelated or unknown endpoints.
As an MCP server, it needs to run a local process and execute its service logic, which is a standard capability for this class of tool. The provided material does not indicate any extra high-privilege system operations or arbitrary code execution unrelated to the Sentry integration.
Based on the description, its primary access scope is Sentry-side error, event, release, and project data; the material does not indicate broad local file read/write access or data permissions beyond its stated purpose. Because it may access organization-level monitoring/event data, least-privilege configuration and data exposure scope still warrant attention.
It comes from an official registry and has a public source repository that can be audited, with updates within the last year—these are strong positive signals. While the community star count is low and the license is unspecified, which merits separate dependency and licensing review, the provided material shows no obvious supply-chain red flags.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.friendlygeorge/sentry-mcp-server" MCP server from askskill: Run: claude mcp add 'io-github-friendlygeorge-sentry-mcp-server' -- npx -y sentry-mcp-server
Connect to Sentry and list the top 5 most frequent errors in my project from the last 24 hours, sorted by affected users. Summarize likely causes and recommended investigation steps for each issue.
A ranked list of frequent errors, impact details, key context, and actionable investigation recommendations.
Review Sentry issues that appeared or spiked after the latest release, compare them with the previous version, identify which errors are likely related to this release, and provide a risk summary.
A comparison of issues before and after release, a list of suspected regressions, and a concise risk assessment.
Summarize my Sentry projects and their current error trends, highlight projects with unusual increases, and briefly explain how I should prioritize them.
A project-level overview, anomaly highlights in trends, and recommended handling priorities.
Search and analyze Sentry issues, events, and traces using natural language.
Query and manage Sentry projects, issues, and events using natural language.
Connect to Sentry to analyze performance, track issues, and trace transactions.
Securely manage databases, SSH sessions, and HTTP workflows for MCP agents.
Run dev checks and get compact error summaries for faster debugging.
Monitor observability issues and auto-fix service errors and billing pipeline problems.