get_issue_detailsLABSCO SUMMARY
Incident debugging in Sentry, with three tools instead of thirty.
It covers the path you actually walk during an incident — open the issue, find the event that matters, follow the trace — and stops there. Being one binary means nothing to install alongside it and a much smaller tool list riding in context.
What it is
Three focused Sentry tools — issue detail with stacktraces and tags, event search inside an issue, and trace detail with the span tree — shipped as one Rust binary.
What you get
- Full issue detail: metadata, tags, stacktraces, and optionally one specific event
- Search within an issue's events using Sentry's own query syntax
- Trace detail with the span tree and timing, for distributed tracing
- A single binary with no Node or Python runtime behind it, and an instant cold start
- A deliberately short tool list, which keeps the tool definitions small in every turn
- SOCKS5 and HTTPS proxy support
Requirements
SENTRY_AUTH_TOKEN and SENTRY_HOST — sentry.io or your own instance hostname. Install with cargo install sentry-mcp, from git, or with mise; the binary is sentry-mcp. Standard proxy environment variables are picked up if you need to route through one.
Setup effort
One command plus a key — cargo install sentry-mcp, then supply credentials
USE CASES
01
Working out what an error actually is
Issue detail brings the stacktrace, tags and metadata back together instead of one at a time.
02
Finding the one occurrence with the context you need
Search inside the issue with Sentry query syntax, then pull that specific event's detail.
03
Following a slow request across services
Trace detail returns the span tree and timings, so the slow hop is visible rather than inferred.
04
Checking whether one release is behind it
Query the issue's events by the tag in question and see how the matches distribute.
3 tools
Listed in project docs. Your client may show a different list.
get_trace_detailssearch_issue_eventsBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- sentry-mcp on PATH
- SENTRY_AUTH_TOKEN in your environment
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"sentry": {
"command": "sentry-mcp",
"env": {
"SENTRY_AUTH_TOKEN": "<YOUR_SENTRY_AUTH_TOKEN>",
"SENTRY_HOST": "sentry.io"
}
}
}
}cargo
TERMINAL
cargo install sentry-mcp
