MCP Sentry para Cursor
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 |
|---|---|
| sentry_capture_exceptionC | Capture and send an exception to Sentry |
| sentry_capture_messageC | Capture and send a message to Sentry |
| sentry_add_breadcrumbC | Add a breadcrumb for debugging context |
| sentry_set_userC | Set user context for Sentry |
| sentry_set_tagC | Set a tag that will be sent with all events |
| sentry_set_contextC | Set custom context data |
| sentry_start_transactionC | Start a performance monitoring transaction |
| sentry_finish_transactionC | Finish the current transaction |
| sentry_start_sessionC | Start a new session for release health monitoring |
| sentry_end_sessionC | End the current session with a specific status |
| sentry_set_releaseC | Set the release version for release health tracking |
| sentry_capture_sessionC | Manually capture a session for server-mode/request-mode |
| sentry_list_projectsB | List all projects in the organization |
| sentry_list_issuesC | List issues for a project |
| sentry_create_releaseC | Create a new release |
| sentry_list_releasesC | List releases for a project |
| sentry_get_organization_statsC | Get organization statistics |
| sentry_create_alert_ruleC | Create an alert rule for a project |
| sentry_resolve_short_idB | Retrieve details about an issue using its short ID. Maps short IDs to issue details, project context and status. |
| sentry_get_eventB | Retrieve a specific Sentry event from an issue. Requires issue ID/URL and event ID. |
| sentry_list_error_events_in_projectC | List error events from a specific Sentry project. View recent errors, frequency patterns and occurrence timestamps. |
| sentry_create_projectC | Create a new project in Sentry. Track deployments, releases and health metrics. |
| sentry_list_issue_eventsC | List events for a specific Sentry issue. Analyze event details, metadata and patterns. |
| sentry_get_issueB | Retrieve and analyze a Sentry issue. Accepts issue URL or ID. |
| sentry_list_organization_replaysC | List replays from a Sentry organization. Monitor user sessions, interactions, errors and experience issues. |
| sentry_setup_projectC | Set up Sentry for a project returning a DSN and instructions for setup. |
| sentry_search_errors_in_fileB | 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 27 tools
Most tools have distinct purposes targeting specific Sentry resources or actions, with clear separation between event capture, issue management, project operations, and monitoring. However, some overlap exists between 'sentry_setup_project' and 'sentry_create_project', and between 'sentry_capture_session' and 'sentry_start_session/end_session', which could cause minor confusion.
All tools follow a consistent 'sentry_verb_noun' pattern with snake_case throughout, making them predictable and easy to parse. The naming convention is uniform across all 27 tools, with no deviations in style or structure.
With 27 tools, the count is borderline high for a Sentry integration, feeling somewhat heavy compared to typical well-scoped servers (3-15 tools). While Sentry is a complex platform, this many tools may overwhelm agents and suggest potential fragmentation or redundancy in the surface.
The tool set provides comprehensive coverage of Sentry's core functionalities, including error/exception capture, issue management, project/release operations, performance monitoring, session tracking, and alerting. There are no obvious gaps, and the surface supports full CRUD/lifecycle workflows for the domain.