sentry-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_BASE_URL | No | Sentry API base URL. Override for self-hosted Sentry. | https://sentry.io/api/0/ |
| SENTRY_AUTH_TOKEN | Yes | Your Sentry auth token (sntrys_...) |
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 |
|---|---|
| list_organizationsA | List all Sentry organizations the authenticated user has access to. Returns id, slug, name, and status for each organization. |
| list_projectsA | List all projects in a Sentry organization. Returns project slug, name, platform, id, and team assignments. |
| list_issuesA | List issues in an organization with optional filters. An issue is a unique error grouped by fingerprint. Returns id, title, level, status, lastSeen, firstSeen, count, and project info. |
| get_issueA | Get full details of a specific issue by numeric ID, including title, culprit, metadata, tags, firstSeen, lastSeen, count, and project info. |
| list_issue_eventsA | List all events (individual occurrences) for a specific issue. Returns event id, message, platform, dateCreated, and tags. Use to find the most recent occurrence. |
| get_eventA | Get full details of a specific event by its ID, including exception values, stack trace, breadcrumbs, tags, and request context. Use this to debug a specific occurrence. |
| list_releasesA | List releases in a Sentry organization. Returns version, name, dateReleased, dateCreated, newGroups, and authors for each release. |
| get_releaseA | Get details of a specific release by version, including commit info, last commit, first/last event, deploy count, new issues, and associated projects. |
| list_teamsB | List teams in a Sentry organization. Returns team id, slug, name, memberCount, and isMember. |
| list_membersB | List members of a Sentry organization. Returns user id, email, name, role, and org role info. |
| get_issue_hashesA | Get the grouping hashes (fingerprint) for a specific issue. Useful to identify why issues are grouped together or to deduplicate across projects. |
| update_issue_statusA | Change the status of a Sentry issue — resolve it, mark it unresolved, ignore it, or set a resolution in the next release. Optionally attach a comment. |
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 12 tools
Each tool targets a distinct resource and action: list_* for listing entities, get_* for retrieving single entities, update_issue_status for modifying an issue, and get_event/list_issue_events for event-level detail. Even closely related tools like list_issues and get_issue are clearly differentiated by summary vs. full detail.
All tool names follow a consistent verb_noun pattern in snake_case (list_organizations, get_release, update_issue_status). Compound nouns like get_issue_hashes and list_issue_events still use the same prefixes and remain predictable.
12 tools is well-scoped for a Sentry server, covering the core resources (organizations, projects, issues, events, releases, teams, members) without redundancy or bloat. Each tool serves a clear purpose in the domain.
The surface covers list/get for all major entities and provides an issue status update action, which is the primary write operation in Sentry. Minor gaps like no get_project or get_organization are negligible because list_projects and list_organizations return sufficient detail, but there is no way to update other resources.