Sentry MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_AUTH | Yes | Your Sentry authentication token with appropriate permissions |
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 |
|---|---|
| list_projectsC | List accessible Sentry projects. View project slugs, IDs, status, settings, features, and organization details. |
| resolve_short_idC | Retrieve details about an issue using its short ID. Maps short IDs to issue details, project context, and status. |
| get_sentry_eventB | Retrieve a specific Sentry event from an issue. Requires issue ID/URL and event ID. |
| list_error_events_in_projectC | List error events from a specific Sentry project. View recent errors, frequency patterns, and occurrence timestamps. |
| create_projectB | Create a new project in Sentry. Track deployments, releases, and health metrics. |
| list_project_issuesC | List issues from a Sentry project. Monitor issue status, severity, frequency, and timing. |
| list_issue_eventsC | List events for a specific Sentry issue. Analyze event details, metadata, and patterns. |
| get_sentry_issueC | Retrieve and analyze a Sentry issue. Accepts issue URL or ID. |
| list_organization_replaysC | List replays from a Sentry organization. Monitor user sessions, interactions, errors, and experience issues. |
| setup_sentryC | Set up Sentry for a project returning a dsn and instructions for setup. |
| search_errors_in_fileC | Search for Sentry errors occurring in a specific file. Find all issues related to a particular file path or filename. |
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 11 tools
Most tools have distinct purposes, but there is some overlap between 'list_project_issues' and 'list_error_events_in_project'—both list issues/errors for a project, which could cause confusion. Other tools like 'get_sentry_event' and 'get_sentry_issue' are clearly differentiated by focusing on events vs. issues.
All tool names follow a consistent verb_noun pattern with underscores, such as 'create_project', 'list_projects', and 'get_sentry_event'. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 11 tools, the count is well-scoped for a Sentry integration, covering key operations like project management, issue/event retrieval, listing, and setup. Each tool appears to serve a specific purpose without being excessive or insufficient.
The toolset provides good coverage for monitoring and debugging in Sentry, including CRUD-like operations (create, list, get) for projects, issues, and events. A minor gap is the lack of update or delete tools for issues or projects, which agents might need for full lifecycle management, but core workflows are well-supported.