get_sentry_issueLABSCO SUMMARY
The stacktrace arrives with the question.
The usual loop is read the alert, open Sentry, copy the trace, paste it somewhere. Here the URL is the input and the trace is already in context, which covers most of the distance between an alert and a diagnosis.
What it is
A Python MCP server for Sentry.io. It retrieves one issue by id or by pasted URL — title, status, level, first-seen and last-seen timestamps, event count and the full stacktrace — and lists a project's issues.
What you get
- One issue retrieved by id or by a Sentry URL you paste
- Title, status, level, first-seen and last-seen timestamps, and event count
- The full stacktrace for that issue
- A project's issues listed, given the project and organisation slugs
- A sentry-issue prompt that drops the issue details into the conversation as context
Requirements
A Sentry auth token, with the project and organisation slugs, passed on the launch command. Runs through uvx, pip or Docker.
Setup effort
One command plus a key — pip install mcp-sentry, then supply credentials
USE CASES
01
Diagnosing an error somebody just linked you
Hand over the Sentry URL and get the stacktrace and status back without opening the dashboard.
02
Judging how bad a problem is before prioritising it
Read the event count and the first-seen and last-seen timestamps rather than the title alone.
03
Reviewing what a project is currently throwing
List the project's issues and work down them, instead of reacting to whichever alert fired loudest.
04
Working out whether a bug is new or long-standing
Compare the issue's first-seen date against the rest of the project's list.
2 tools
Listed in project docs. Your client may show a different list.
get_list_issuesBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- pip on PATH (or uvx / Docker for those routes)
- A Sentry auth token (--auth-token)
- Your Sentry project slug (--project-slug) and organization slug (--organization-slug)
Where it runs
All 4 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install mcp-sentryMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"sentry": {
"command": "uvx",
"args": [
"mcp-sentry",
"--auth-token",
"<YOUR_SENTRY_TOKEN>",
"--project-slug",
"<YOUR_PROJECT_SLUG>",
"--organization-slug",
"<YOUR_ORGANIZATION_SLUG>"
]
}
}
}Claude Desktop — Docker
CLAUDE DESKTOP — DOCKER · JSON
{
"mcpServers": {
"sentry": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp/sentry",
"--auth-token",
"<YOUR_SENTRY_TOKEN>",
"--project-slug",
"<YOUR_PROJECT_SLUG>",
"--organization-slug",
"<YOUR_ORGANIZATION_SLUG>"
]
}
}
}Claude Desktop — pip
CLAUDE DESKTOP — PIP · JSON
{
"mcpServers": {
"sentry": {
"command": "python",
"args": [
"-m",
"mcp_sentry",
"--auth-token",
"<YOUR_SENTRY_TOKEN>",
"--project-slug",
"<YOUR_PROJECT_SLUG>",
"--organization-slug",
"<YOUR_ORGANIZATION_SLUG>"
]
}
}
}Zed
ZED · JSON
{
"context_servers": {
"mcp-sentry": {
"command": "python",
"args": [
"-m",
"mcp_sentry",
"--auth-token",
"<YOUR_SENTRY_TOKEN>",
"--project-slug",
"<YOUR_PROJECT_SLUG>",
"--organization-slug",
"<YOUR_ORGANIZATION_SLUG>"
]
}
}
}
