Sentry MCP integration

Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug.

Add a custom symbol source to a Sentry project.

Invites a new member (or re-invites an existing non-accepted member) to a Sentry organization via email, allowing specification of organization and team roles.

Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user.

Adds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization.

Grants a Sentry team access to a Sentry project within the specified Sentry organization.

Bulk mutate various attributes on issues within an organization.

Permanently removes issues from an organization.

Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system.

Creates a Sentry dashboard with widgets for an organization; organization_id_or_slug and specified project IDs must be valid, and start/end datetimes (if absolute range) must form a logical ISO 8601 range.

Links a Sentry user to an external identity provider's user within a Sentry organization; the Sentry user must be an organization member, an active integration for the provider must be configured, and external_id is typically required for the external user.

Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations.

Creates a new monitor (type 'cron_job') within a Sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status, owner, and muting preferences for incidents.

Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team.

Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration.

Creates a Sentry project alert rule by defining conditions, actions, and optional filters using specific JSON structures (detailed in parameter descriptions) to automate responses to event patterns for an existing organization and project.

Registers a new webhook subscription for a Sentry project to send HTTP POST notifications to a specified URL for given events, provided the project has the 'servicehooks' feature enabled.

Creates a new deploy record in Sentry to track the introduction of a release version into a specific environment.

Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.

Creates a new Sentry team (SCIM group) within an organization via the SCIM API.

Links an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation uuid.

Creates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules.

Creates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails.

Deletes a custom integration (Sentry App) by its ID or slug.

⚠️ This endpoint is currently in beta and may be subject to change.

Bulk delete alerts for a given organization.

Permanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization.

Unlinks an external issue (e.g., from Jira/GitHub), identified by external_issue_id, from the Sentry app installation specified by uuid.

Unlinks a previously established external team from a Sentry team; this action does not delete either the Sentry team or the external team.

Deletes the link between an external user (from an integration provider like GitHub, Slack, GitLab, or MS Teams) and a Sentry user within the specified organization.