Sentry Issues MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_single_eventC | get issue event by inputting sentry issue event url or sentry issue event id |
| get_project_eventsC | get issue events by inputting sentry organization id or slug and sentry project name or slug |
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 2 tools
The two tools have clearly distinct purposes: get_project_events retrieves multiple events for a project, while get_single_event retrieves a single event by its URL or ID. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (get_project_events, get_single_event) with clear, descriptive names that indicate their specific functions. The naming is uniform and predictable.
With only 2 tools, the server feels too thin for a Sentry Issues domain, as it lacks essential operations like creating, updating, or listing issues, which are core to issue management workflows. This minimal set limits functionality significantly.
The tool surface is severely incomplete for Sentry Issues, covering only event retrieval. It misses critical operations such as listing issues, creating issues, updating issue status, or deleting issues, leaving agents unable to perform basic issue lifecycle tasks.