utapyngo/sentry-mcp-rs

A fast, lightweight MCP server for Sentry, written in Rust.
Why sentry-mcp?
Compared to the official Node.js server:
- **Memory:** 10x less RAM usage
- **Startup:** instant cold start
- **Disk:** single binary, no runtime dependencies
- **Tokens:** fewer tools = smaller tool list in context
Features
This MCP server provides tools to interact with Sentry's API:
- **get_issue_details** - Retrieve detailed information about a Sentry issue including metadata, tags, stacktraces, and optionally a specific event
- **get_trace_details** - Retrieve trace details including span tree and timing information for distributed tracing analysis
- **search_issue_events** - Search events within an issue using Sentry's query syntax
Installation
From crates.io:
From GitHub:
Or with mise:
The binary will be installed as sentry-mcp.
Configuration
Required environment variables:
- SENTRY_AUTH_TOKEN - Your Sentry API authentication token
- SENTRY_HOST - Your Sentry instance hostname (e.g., sentry.io)
Optional:
- SOCKS_PROXY - SOCKS5 proxy URL (e.g., socks5://127.0.0.1:1080)
- HTTPS_PROXY - HTTPS proxy URL
MCP Client Configuration
Add to your MCP client configuration:
Or without installation using mise:
Development
Clone the repository and create a .env file:
Build and test with MCP Inspector:
Or configure MCP client to use the script:
Tools
get_issue_details
Retrieve detailed information about a specific Sentry issue.
**Parameters:**
- issue_url - Full Sentry issue URL (alternative to the parameters below)
- organization_slug - Organization slug (required if issue_url not provided)
- issue_id - Issue ID like PROJECT-123 or numeric ID (required if issue_url not provided)
- event_id - Specific event ID to fetch instead of latest (optional)
get_trace_details
Retrieve trace details for distributed tracing analysis.
**Parameters:**
- organization_slug - Organization slug
- trace_id - 32-character hex trace ID
search_issue_events
Search events within an issue using Sentry's query syntax.
**Parameters:**