sentry-mcp-rs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTPS_PROXY | No | HTTPS proxy URL | |
| SENTRY_HOST | Yes | Your Sentry instance hostname (e.g., sentry.io) | |
| SOCKS_PROXY | No | SOCKS5 proxy URL (e.g., socks5://127.0.0.1:1080) | |
| SENTRY_AUTH_TOKEN | Yes | Your Sentry API authentication token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trace_detailsA | Retrieve trace details including span tree and timing information. Useful for analyzing distributed system performance. |
| get_issue_detailsA | Retrieve detailed information about a specific Sentry issue including metadata, tags, and optionally an event. Accepts either an issueUrl OR (organizationSlug + issueId). |
| search_issue_eventsB | Search events for a specific issue using a query string. Returns matching events with their details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: issue details, trace details, and event search. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern using snake_case, e.g., get_issue_details, get_trace_details, search_issue_events.
Three tools is on the lower side but still reasonable for a focused Sentry server covering core issue and trace functionality.
The set lacks essential CRUD operations like listing issues, updating issue status, or resolving issues, leaving significant gaps for a comprehensive Sentry workflow.