Sentry MCP server

Read from the package source without running it. The installed server may list more.

• add_member_to_organization

  Add or invite a member to an organization with optional role assignment and team membership. Sends an email invitation by default unless disabled.

• add_member_to_team

  Add an organization member to a team. The operation returns different success codes based on context: 201 if successfully added, 202 if an access request is generated (pending approval), or 204 if the member is already on the team. Permission requirements vary based on the organization's 'Open Membership' setting and token type.

• bulk_update_issueswrite action
• create_alert_for_organizationwrite action

  Creates a new alert for an organization to monitor issues and trigger notifications based on specified conditions. This endpoint is currently in beta and supports the New Monitors and Alerts system.

• create_dashboardwrite action

  Create a new dashboard for an organization to visualize and monitor project metrics, events, and custom data. Dashboards can include widgets, project filters, environment filters, and saved search criteria.

• create_data_forwarder_for_organizationwrite action

  Creates a new data forwarder for an organization to forward data to external providers like Segment, Amazon SQS, or Splunk. Only one data forwarder per provider is allowed per organization.

• create_deploy_for_releasewrite action

  Create a deployment record for a specific release version to a target environment. This tracks when and where a release was deployed, optionally linking it to specific projects.

• create_metric_monitor_for_projectwrite action

  Create a metric-based monitor for a project to detect issues based on error counts, performance metrics, or custom measurements. This beta endpoint supports multiple monitor types including threshold-based, change-based, and dynamic anomaly detection.

• create_monitorwrite action

  Create a new monitor for uptime or performance tracking within an organization. The monitor will be associated with a specific project and can be configured with custom check-in rules and notification settings.

• create_organization_memberwrite action

  Provision a new organization member via SCIM protocol. The member will be assigned the organization's default role unless a specific role is provided.

• create_saved_querywrite action

  Create a new saved query for an organization to store custom Discover search configurations, including filters, fields, aggregations, and visualization settings.

• create_teamwrite action

  Create a new team within an organization. At least one of `name` or `slug` must be provided in the request body.

• create_team_in_organizationwrite action

  Create a new team within an organization using SCIM Groups protocol. The team is initialized with an empty member set, and the display name is normalized to lowercase with spaces converted to dashes.

• delete_alertwrite action

  Permanently deletes an alert from a workflow. This endpoint is currently in beta and supported by New Monitors and Alerts.

• delete_alerts_bulkwrite action

  Bulk delete alerts for an organization, optionally filtered by a search query. This endpoint is currently in beta and supported by New Monitors and Alerts.

• delete_data_forwarder_for_organizationwrite action

  Permanently deletes a data forwarder from an organization, including all associated project-specific overrides.

• delete_discover_saved_querywrite action

  Permanently delete a saved Discover query from an organization. This action cannot be undone.

• delete_external_userwrite action

  Remove the link between an external provider user and a Sentry user account, effectively disconnecting the external identity from the organization.

• delete_monitorwrite action

  Permanently delete a monitor (detector) from an organization. This beta endpoint is part of the New Monitors and Alerts system and may not yet be visible in the UI.

• delete_monitor_or_monitor_environmentswrite action

  Delete a monitor or specific monitor environments. If environment names are provided, only those environments are deleted; otherwise, the entire monitor is deleted.

• delete_monitors_bulkwrite action

  Bulk delete monitors for an organization, optionally filtered by search criteria. This beta endpoint supports the New Monitors and Alerts system.

• delete_organization_dashboardwrite action

  Delete an organization's custom dashboard or tombstone a pre-built dashboard to effectively remove it from the organization.

• delete_organization_integrationwrite action

  Remove an integration from an organization. This operation requires both the Integration and OrganizationIntegration database entries to exist for the specified organization and integration.

• delete_organization_issueswrite action

  Permanently remove issues from an organization. Specify issues by ID for precise deletion, or use query filters to target multiple issues. Returns success even if no matching issues are found.

• delete_organization_memberwrite action

  Remove a member from an organization. This operation permanently deletes the member's association with the organization.

• delete_organization_releasewrite action

  Permanently delete a release from an organization, including all associated files and artifacts. This action cannot be undone.

• get_alert

  Retrieve a specific alert (workflow) by its ID. This endpoint is part of the New Monitors and Alerts system and is currently in beta.

• get_artifact_install_details

  Retrieve installation and distribution details for a preprod artifact, including installability status, install URL, download metrics, and iOS code signing information.

• get_artifact_size_analysis

  Retrieve size analysis results for a build artifact, including download and install size metrics. Optionally compare against a base artifact to see size differences.

• get_discover_saved_query

  Retrieve a saved Discover query by its ID within a specific organization. This returns the full configuration and metadata of the saved query.

• get_event_counts_for_organization
• get_events_timeseries

  Retrieves event data for an organization as a timeseries, supporting single or multiple axes with optional grouping by top events. Results can be filtered by environment, time range, and custom query syntax.

• get_monitor

  Retrieves detailed information about a specific monitor, including its configuration, status, and settings.

• get_monitor_detector

  Retrieve detailed information about a specific monitor (detector). This endpoint is part of the New Monitors and Alerts system and is currently in beta.

• get_organization

  Retrieve detailed information about a specific organization, including membership access levels and associated teams.

• get_organization_dashboard

  Retrieve detailed information about a specific custom dashboard within an organization, including its configuration and contents.

• get_organization_events_count_by_project

  Retrieve summarized event counts aggregated by project for an organization. Use this to analyze event volume, filtering by category (errors, transactions, attachments, replays, profiles), outcome status, and other dimensions.

• get_organization_integration

  Retrieve a specific integration installed on an organization. Both the integration and its organization-specific configuration must exist.

• get_organization_member

  Retrieve details for a specific organization member, including pending invite status if the member has been approved by owners or managers but hasn't yet accepted the invitation.

• get_organization_release

  Retrieve detailed information about a specific release within an organization, including optional health metrics, adoption stages, and summary statistics.

• get_replay_count_for_issues_or_transactions

  Retrieve the count of replays associated with specified issues, transactions, or replay IDs within an organization. Use the query parameter to filter by issue ID, transaction name, or replay ID.

• get_replay_instance

  Retrieve detailed information about a specific replay session by its ID. Returns comprehensive replay data including metadata, events, and user interactions.

• get_repository

  Retrieves detailed metadata for a single repository within an organization, identified by its owner and repository name.

• get_repository_sync_status

  Retrieves the synchronization status of repositories for an integrated organization, showing which repositories are currently syncing and their progress.

• get_spike_protection_notification_action

  Retrieve a specific Spike Protection Notification Action that notifies organization members when spike detection is triggered. This action defines how and which members are alerted through services like Slack or email.

• get_test_results_aggregates_for_repository

  Retrieves aggregated test result metrics for a specific repository within an organization, with optional filtering by branch. Metrics can be scoped to a particular time period via query parameters.

• link_external_user

  Link a user from an external provider (such as GitHub, Slack, Jira, or GitLab) to a Sentry user account, enabling cross-platform identity mapping and integration.

• list_alerts

  Retrieve a list of alerts for an organization. This endpoint is currently in beta and supports the New Monitors and Alerts feature.

• list_checkins_for_monitor

  Retrieve all check-ins recorded for a specific monitor, showing the history of uptime verification events.

• list_data_forwarders_for_organization

  Retrieves all data forwarders configured for a specific organization. Data forwarders enable automatic forwarding of events and data to external destinations.

• list_integration_providers

  Retrieve information about all available integration providers for an organization, with optional filtering by a specific provider type.

• list_monitors_for_organization

  Retrieves all monitors for an organization, including their nested environments. Results can be filtered by specific projects or environments, and optionally filtered by monitor owner.

• list_organization_client_keys

  Retrieve all client keys (DSNs) across projects in an organization, with optional filtering by team and key status. Results are paginated for efficient retrieval of large key sets.

• list_organization_dashboards

  Retrieve all custom dashboards associated with an organization. Results can be paginated to control the number of dashboards returned per request.

• list_organization_discover_saved_queries

  Retrieve all saved Discover queries associated with an organization, with optional filtering by query name and pagination support.

• list_organization_environments

  Retrieves all environments for a specified organization, with optional filtering by visibility status. Use this to discover available deployment environments and their configurations.

• list_organization_integrations

  Retrieve all available integrations for an organization, with optional filtering by provider and features. Use includeConfig to fetch third-party configuration details if needed.

• list_organization_issues

  Retrieve a list of issues for an organization with optional filtering, search, and pagination. By default, only unresolved issues are returned unless a custom query is provided.

• list_organization_members

  Retrieve all members of an organization, including pending invitations that have been approved by owners or managers but not yet accepted by invitees.

• list_organization_monitors

  Retrieve all monitors configured for an organization. This endpoint supports the new monitoring and alerting system and allows filtering by monitor properties such as name, type, and assignee.

• list_organization_projects

  Retrieve all projects associated with a specific organization. Returns a list of projects bound to the organization identified by ID or slug.

• list_organization_replay_selectors

  Retrieve a list of replay selectors configured for an organization, with optional filtering by environment, query criteria, and pagination controls.

• list_organization_replays

  Retrieve a paginated list of session replays for an organization, with optional filtering by environment and structured query parameters.

• list_organization_scim_members

  Retrieves a paginated list of SCIM-provisioned members in an organization. Use SCIM filter expressions to narrow results or exclude specific attributes from the response.

• list_organization_teams

  Retrieves a list of all teams associated with a specific organization. Optionally filter the response to exclude project details for a lighter payload.

• list_organization_teams_scim

  Retrieve a paginated list of teams in an organization using SCIM Groups protocol. Note that the members field is capped at 10,000 members per team.

• list_organization_trusted_relays

  Retrieve a list of all trusted relays configured for an organization. Relays are used to forward events and requests securely within the organization's infrastructure.

• list_organizations

  Retrieve a list of organizations accessible to the authenticated session. For user-bound contexts, returns all member organizations; for API key requests, returns only the organization associated with that key.

• list_release_deploys

  Retrieve all deployments for a specific release version within an organization. Returns deployment history and status information for the given release.

• list_release_health_session_statistics

  Retrieves time series data for release health session statistics across projects in an organization. Results are aggregated by specified intervals and grouped by optional dimensions, with automatic rounding to align with the selected time interval.

• list_release_threshold_statuses

  Retrieve the health statuses of release thresholds within a specified time range. Returns threshold statuses keyed by release version and project, including full threshold details and derived health indicators. **Note: This is an experimental Alpha API subject to change.**

• list_repositories_for_owner

  Retrieves a paginated list of repositories owned by a specified owner within an organization. Results can be filtered by name substring.

• list_repository_branches

  Retrieves a paginated list of branches for a specified repository, with optional filtering by branch name substring.

• list_repository_commits

  Retrieve a paginated list of commits for a specific repository within an organization. Use this to view the commit history and details for a given repository.

• list_repository_tokens_for_owner

  Retrieves a paginated list of repository tokens for a specified owner within an organization. Use this to view all tokens associated with a particular repository owner.

• list_sentry_apps

  Retrieve all custom integrations (Sentry Apps) created by an organization. This returns the organization's internal integrations that extend Sentry's functionality.

• list_spike_protection_notifications

  Retrieve all Spike Protection Notification Actions configured for an organization. These actions notify designated members via services like Slack or email when spike protection is triggered.

• list_test_results_for_repository

  Retrieves a paginated list of test results for a specific repository, with optional filtering by test status, branch, and name substring matching.

• list_test_suites_for_repository

  Retrieves all test suites associated with a repository's test results, with optional filtering by name substring.

• list_user_teams_in_organization

  Retrieve all teams within an organization that the authenticated user has access to. This endpoint requires user authentication tokens and is useful for discovering team membership and permissions.

• regenerate_repository_upload_tokenwrite action

  Regenerates an existing repository upload token, invalidating the previous token and returning a new one for repository uploads.

• remove_member_from_teamwrite action

  Remove an organization member from a specific team. Requires appropriate authorization scopes; org:read scope can only remove yourself from teams you belong to.

• resolve_event_id

  Resolves an event ID to retrieve the associated project slug, internal issue ID, and internal event ID for a given organization.

• resolve_short_id

  Resolve a short issue ID to retrieve the associated project slug and group (issue) details. This allows you to look up full issue information using a condensed identifier.

• search_events_in_table_format

  Retrieves a table of events from a specified organization matching your query criteria. Use this to explore event data with selected fields and optional filtering; not intended for full data exports.

• sync_repositories_for_owner

  Synchronizes repositories from a specified owner with an integrated GitHub organization, ensuring the local repository list matches the current state in GitHub.

• update_alertwrite action

  Updates an existing alert configuration including its name, enabled status, trigger conditions, action filters, and connected monitors. This endpoint supports the New Monitors and Alerts system and is currently in beta.

• update_data_forwarderwrite action

  Updates a data forwarder configuration for an organization, or creates/modifies project-specific overrides. Organization-level updates require the full configuration including project IDs, while project-level overrides only need the project ID, overrides object, and enabled status.

• update_discover_saved_querywrite action

  Modify an existing saved Discover query, including its name, filters, fields, visualization settings, and aggregations.

• update_external_userwrite action

  Update the details of an external user account linked to a Sentry user. This synchronizes user information across integrated external providers like GitHub, Slack, Jira, or GitLab.

• update_metric_alert_rulewrite action
• update_monitorwrite action

  Update an existing monitor's configuration, status, ownership, and notification settings. Changes to the slug will require updates to any instrumented check-in calls referencing the monitor.

• update_monitor_detectorwrite action

  Update an existing metric monitor with new configuration, data sources, detection rules, and alert connections. This beta endpoint supports threshold-based, change-based, and dynamic anomaly detection monitors.

• update_organizationwrite action
• update_organization_alerts_bulkwrite action

  Bulk enable or disable alerts across an organization, optionally filtered by search query. This beta endpoint supports the New Monitors and Alerts system.

• update_organization_dashboardwrite action

  Update an organization's custom dashboard configuration, including its title, widgets, filters, and display settings. Supports bulk edits to widget arrangements, queries, fields, and display types.

• update_organization_member_roleswrite action

  Update an organization member's roles at both the organization and team levels. Requires user auth tokens and enforces permission hierarchy—you can only assign roles with equal or lower permissions than your own.

• update_organization_member_team_rolewrite action

  Update an organization member's role within a specific team. The member must already be part of the team. Note that organization admins, managers, and owners automatically receive a minimum team role of admin on all their teams.

• update_organization_monitors_enabled_statewrite action

  Bulk enable or disable monitors across an organization, optionally filtered by search criteria. This beta endpoint supports the New Monitors and Alerts system.

• update_organization_releasewrite action

  Update release metadata including repository references, deployment URL, and release date. Allows modification of commit information, external links, and timing details for an existing release.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 55% of 1,119 Developer tools servers

Tools

100

the typical Developer tools server has 7

Tools that change things

40%

typical: 5%. Fewer write tools means less an agent can break

GitHub stars

31

more than 90% of 855 Developer tools servers

Downloads a week

154

more than 67% of 436 Developer tools servers with a package

Sentry: common questions

Is Sentry MCP server safe?

Mostly: it is graded B (80/100). Read the Sentry safety report

How do I install Sentry?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Sentry need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Sentry maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.2.

What can I use instead of Sentry?

Servers from other publishers that do the same job: HomeLab Monitor MCP server, maintenant MCP server and Jira Alerts (JSM Operations) MCP server.

How does Sentry compare with other Developer tools MCP servers?

safety score 80/100 (higher than 55% of 1,119 Developer tools servers); tools 100 (the typical Developer tools server has 7); tools that change things 40% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.