Sentry MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_DSN | No | Your Sentry DSN (Data Source Name) | |
| 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 targeting different resources like projects, issues, events, replays, and errors, with clear boundaries. However, 'get_sentry_event' and 'list_issue_events' could be slightly confusing as both relate to issue events, though the former retrieves a specific event while the latter lists events, which is clarified in descriptions.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_project', 'list_projects', 'get_sentry_issue', and 'search_errors_in_file'. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 11 tools, the count is well-scoped for a Sentry monitoring and debugging server. It covers core operations like project management, issue and event retrieval, error searching, and setup without feeling excessive or insufficient for the domain.
The tool surface provides strong coverage for monitoring and debugging in Sentry, including CRUD-like operations for projects and issues, event listing, error searching, and setup. A minor gap is the lack of tools for updating or deleting resources, such as updating issue status or deleting projects, but agents can still perform key workflows effectively.