get_release_healthLABSCO SUMMARY
Built for the question asked right after a release ships: is this version worse than the last one?
It answers that directly — crash-free rates for both versions side by side, the issues that are new in this build, and the ones that came back — and lets the agent leave a comment on the issue it found so the finding lands where the team already looks.
What it is
An unofficial Sentry server built around releases: health and adoption figures, the issues tied to a specific release, deploy history, and issue comments.
What you get
- Crash-free users, crash-free sessions, and session and user counts for a release
- Adoption percentages, both session-based and user-based
- A side-by-side crash-free comparison between two releases
- Issues first seen in a specific release
- Issues that regressed in a specific release
- Deployment history for a release
- A comment posted onto a Sentry issue
Requirements
Four environment values — SENTRY_PERSONAL_TOKEN, SENTRY_ORG, SENTRY_PROJECT and SENTRY_BASE_URL — and uv installed, since it runs through uvx.
Setup effort
One command plus a key — claude mcp add sentry-companion -e SENTRY_PERSONAL_TOKEN=<YOUR_SENTRY_PERSONAL_TOKEN> -e SENTRY_ORG=<YOUR_SENTRY_ORG> -e SENTRY_PROJECT=<YOUR_SENTRY_PROJECT> -e SENTRY_BASE_URL=https://us.sentry.io -- uvx sentry-companion-mcp
USE CASES
01
Deciding whether to roll back a release
Compare crash-free users against the previous version, then look at what is new in this one before making the call.
02
Watching a rollout land
Read adoption by sessions and by users to see how much of the base is actually on the new build yet.
03
Catching a bug that came back
List the issues that regressed in this release — the ones a new-issues list would miss because they are not new.
04
Tying a spike to a deploy
Read the deploy history for the release and line it up against when the health numbers moved.
05
Leaving the finding where the team will see it
Post the conclusion as a comment on the Sentry issue instead of pasting it into chat.
7 tools
Listed in project docs. Your client may show a different list.
get_release_adoptioncompare_releasesget_release_new_issuesget_release_regressed_issuesget_release_deploysadd_issue_commentBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- uvx on PATH
- SENTRY_PERSONAL_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
claude mcp add sentry-companion -e SENTRY_PERSONAL_TOKEN=<YOUR_SENTRY_PERSONAL_TOKEN> -e SENTRY_ORG=<YOUR_SENTRY_ORG> -e SENTRY_PROJECT=<YOUR_SENTRY_PROJECT> -e SENTRY_BASE_URL=https://us.sentry.io -- uvx sentry-companion-mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"sentry-companion": {
"type": "stdio",
"command": "uvx",
"args": [
"sentry-companion-mcp"
],
"env": {
"SENTRY_PERSONAL_TOKEN": "<YOUR_SENTRY_PERSONAL_TOKEN>",
"SENTRY_ORG": "<YOUR_SENTRY_ORG>",
"SENTRY_PROJECT": "<YOUR_SENTRY_PROJECT>",
"SENTRY_BASE_URL": "https://us.sentry.io"
}
}
}
}
