# How to integrate Sentry MCP with Claude Code

```json
{
  "title": "How to integrate Sentry MCP with Claude Code",
  "toolkit": "Sentry",
  "toolkit_slug": "sentry",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/sentry/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/sentry/framework/claude-code.md",
  "updated_at": "2026-05-12T10:25:30.127Z"
}
```

## Introduction

Manage your Sentry directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Sentry with

- [ChatGPT](https://composio.dev/toolkits/sentry/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/sentry/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/sentry/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/sentry/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/sentry/framework/codex)
- [Cursor](https://composio.dev/toolkits/sentry/framework/cursor)
- [VS Code](https://composio.dev/toolkits/sentry/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/sentry/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/sentry/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/sentry/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/sentry/framework/cli)
- [Google ADK](https://composio.dev/toolkits/sentry/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/sentry/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/sentry/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/sentry/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/sentry/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/sentry/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Sentry to Claude Code

### Connecting Sentry to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the Sentry MCP server, and what's possible with it?

The Sentry MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Sentry account. It provides structured and secure access to your projects, teams, and monitoring data, so your agent can perform actions like managing alerts, configuring dashboards, inviting team members, and tracking error monitors on your behalf.
- Project and team management: Your agent can access project details, add teams to projects, and manage organization teams, helping you stay on top of collaboration and permissions.
- Organization member onboarding: Effortlessly invite new members to your Sentry organization or add existing members to teams via email, streamlining team setup and access control.
- Automated alert and monitor creation: Set up metric alert rules and create scheduled monitors (like cron jobs) to track incidents and automate error tracking for projects.
- Dashboard and widget configuration: Instruct your agent to create custom dashboards with widgets tailored to your organization's needs, enabling focused error monitoring and visualization.
- User identity and email management: Link users to external identity providers or manage user emails, keeping your organization’s authentication and contact information up to date.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `SENTRY_ACCESS_PROJECT_INFORMATION` | Access project information | Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug. |
| `SENTRY_ADD_A_SYMBOL_SOURCE_TO_A_PROJECT` | Add a symbol source to a project | Tool to add a custom symbol source to a Sentry project. Use when configuring symbol sources for crash symbolication. |
| `SENTRY_ADD_ORGANIZATION_MEMBER_VIA_EMAIL` | Add organization member via email | 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. |
| `SENTRY_ADD_REMOVE_USER_EMAIL_BY_ID` | Add or remove user email by id | Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user. |
| `SENTRY_ADD_TEAM_MEMBER_IN_ORGANIZATION` | Add team member in organization | 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. |
| `SENTRY_ADD_TEAM_TO_PROJECT` | Add team to project | Grants a Sentry team access to a Sentry project within the specified Sentry organization. |
| `SENTRY_BULK_MUTATE_AN_ORGANIZATIONS_ISSUES` | Bulk mutate an organization's issues | Bulk mutate various attributes on issues within an organization. Use when you need to update status, priority, assignment, or other attributes for multiple issues at once. Maximum of 1000 issues can be mutated, with a 100 issue limit per request. |
| `SENTRY_BULK_REMOVE_AN_ORGANIZATIONS_ISSUES` | Bulk remove an organization's issues | Permanently removes issues from an organization. If IDs are provided, queries and filtering are ignored. Maximum of 1000 issues can be removed at once. |
| `SENTRY_CREATE_AN_ALERT_FOR_AN_ORGANIZATION` | Create an alert for an organization | Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system. Use when you need to set up automated alerting for issues based on trigger conditions and filters. Note: This endpoint is currently in beta and may change. |
| `SENTRY_CREATE_DASHBOARD_WITH_WIDGETS` | Create dashboard with widgets | 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. |
| `SENTRY_CREATE_EXTERNAL_USER_FOR_ORGANIZATION` | Create external user for organization | 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. |
| `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` | Create organization alert rule | Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations. |
| `SENTRY_CREATE_ORGANIZATION_MONITOR` | Create organization monitor | 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. |
| `SENTRY_CREATE_ORGANIZATION_TEAM` | Create organization team | Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team. |
| `SENTRY_CREATE_PROJECT_KEY_WITH_OPTIONAL_RATE_LIMITING` | Create project key with optional rate limiting | Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration. |
| `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` | Create project rule for alerts | 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. |
| `SENTRY_CREATE_PROJECT_WEBHOOK_SUBSCRIPTION` | Create project webhook subscription | 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. |
| `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` | Create release deploy for org | Creates a new deploy record in Sentry to track the introduction of a release version into a specific environment. |
| `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` | Create release for organization | Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization. |
| `SENTRY_CREATE_SCIM_GROUP_FOR_ORGANIZATION` | Create scim group for organization | Creates a new Sentry team (SCIM group) within an organization via the SCIM API. Requirements: - Organization must have SCIM enabled (requires Business Plan with SAML2) - Must use a SCIM bearer token (generated when SCIM is enabled) - Token must have 'team:admin' or 'team:write' scope Behavior: - A URL-friendly slug is auto-generated from displayName (e.g., 'My Team' → 'my-team') - Team is created with an empty member set - Members must be added separately through SCIM member operations - Returns SCIM 2.0 Group resource with unique ID Use this for SCIM provisioning workflows with identity providers like Okta or Azure AD. |
| `SENTRY_CREATE_SENTRY_EXTERNAL_ISSUE_LINK` | Create sentry external issue link | Links an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation `uuid`. |
| `SENTRY_CREATE_TEAM_PROJECT_FOR_ORGANIZATION` | Create team project for organization | Creates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules. |
| `SENTRY_CREATE_USER_FOR_SAML_INTEGRATION` | Create user for SAML integration | Creates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails. |
| `SENTRY_DELETE_A_CUSTOM_INTEGRATION` | Delete a custom integration | Deletes a custom integration (Sentry App) by its ID or slug. Use when you need to permanently remove a custom integration from your organization. Requires org:admin scope. |
| `SENTRY_DELETE_AN_ALERT` | Delete an alert | ⚠️ This endpoint is currently in beta and may be subject to change. Deletes an alert. Use when you need to permanently remove an alert from an organization. |
| `SENTRY_DELETE_BULK_ALERTS` | Delete bulk alerts | Bulk delete alerts for a given organization. Use when you need to delete multiple alerts at once. ⚠️ This endpoint is currently in beta and may be subject to change. |
| `SENTRY_DELETE_DSYMS_FOR_PROJECT` | Delete dsyms for project | Permanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization. |
| `SENTRY_DELETE_EXTERNAL_ISSUE_BY_UUID` | Delete external issue by uuid | Unlinks an external issue (e.g., from Jira/GitHub), identified by `external_issue_id`, from the Sentry app installation specified by `uuid`. |
| `SENTRY_DELETE_EXTERNAL_TEAM_BY_ID` | Delete an external team by id | Unlinks a previously established external team from a Sentry team; this action does not delete either the Sentry team or the external team. |
| `SENTRY_DELETE_EXTERNAL_USER_FROM_ORGANIZATION` | Delete external user from organization | 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. This removes the association but does not delete the Sentry user itself. Requires org:admin or org:write permissions. |
| `SENTRY_DELETE_MEMBER_FROM_TEAM` | Delete member from team | Removes an organization member from a Sentry team, revoking their team-specific permissions, provided the member is currently part of that team. |
| `SENTRY_DELETE_ORGANIZATION_ALERT_RULE` | Delete organization alert rule | Permanently deletes a metric alert rule from a Sentry organization. This action removes the specified metric alert rule, stopping all monitoring and notifications associated with it. The deletion is immediate and cannot be undone. Metric alert rules monitor aggregated metrics (like error rates, latency, or custom metrics) and are different from issue alert rules which trigger on individual events. **Important**: Metric alert rules require a Sentry Business or Enterprise plan. If your organization is on a different plan, this endpoint will return a 404 Not Found error. **Common Use Cases**: - Cleaning up outdated or unnecessary alert rules - Removing test alert rules after validation - Decommissioning monitoring for deprecated services **Returns**: Success message on deletion (HTTP 202), or error details if the rule doesn't exist or cannot be deleted. |
| `SENTRY_DELETE_ORGANIZATION_DASHBOARD` | Delete organization dashboard | Deletes a custom dashboard or tombstones (marks as deleted) a pre-built dashboard within a Sentry organization. |
| `SENTRY_DELETE_ORGANIZATION_DISCOVER_QUERY` | Delete organization discover query | Permanently removes a specific saved Discover query (a configuration for exploring event data) from a Sentry organization. This action requires one of the following scopes: org:admin, org:read, or org:write. The Discover saved queries feature is only available on Business and Enterprise plans. |
| `SENTRY_DELETE_ORGANIZATION_INTEGRATION` | Delete organization integration | Permanently removes an integration installation from a Sentry organization. This action requires the numeric integration ID, which can be obtained by first calling retrieve_organization_integrations_list. Required permissions: org:admin or org:integrations scope. |
| `SENTRY_DELETE_ORGANIZATION_ISSUE` | Delete organization issue | Permanently deletes a specific Sentry issue, identified by its ID, from an organization; this operation is irreversible and idempotent. |
| `SENTRY_DELETE_ORGANIZATION_MEMBER` | Delete organization member | Permanently removes a member from a Sentry organization, revoking their access to that organization and all its associated projects. |
| `SENTRY_DELETE_ORGANIZATION_MONITOR` | Delete organization monitor | Deletes a Sentry cron monitor or, if `environment` is specified, only specific environments within that monitor. |
| `SENTRY_DELETE_ORGANIZATION_RELEASE` | Delete organization release | Permanently and irreversibly removes a Sentry release, including all its associated files, identified by its version from the specified organization. |
| `SENTRY_DELETE_ORGANIZATION_RELEASE_FILE` | Delete organization release file | Tool to delete a file from an organization release. Use when you need to remove a specific file associated with a release version in an organization. |
| `SENTRY_DELETE_ORG_NOTIFICATION_ACTION` | Delete org notification action | Deletes a specific Spike Protection Notification Action for a Sentry organization, where `action_id` must be a valid action associated with the `organization_id_or_slug`. |
| `SENTRY_DELETE_PROJECT_BY_ID` | Delete project by id | Schedules a Sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins. |
| `SENTRY_DELETE_PROJECT_HOOK` | Delete project hook | Deletes a specific service hook from a Sentry project using its organization, project, and hook identifiers. |
| `SENTRY_DELETE_PROJECT_ISSUES` | Delete project issues | Permanently removes specified issues from a Sentry project; if no issue IDs are provided, it removes the oldest 1000 issues. |
| `SENTRY_DELETE_PROJECT_KEY` | Delete project key | Permanently deletes a specific client key (DSN) for a project, preventing it from being used to send events to Sentry. |
| `SENTRY_DELETE_PROJECT_MONITOR` | Delete project monitor | Deletes a Sentry monitor, or optionally only its specified environments, for a given project. |
| `SENTRY_DELETE_PROJECT_REPLAY` | Delete project replay | Permanently deletes a specific Sentry session replay (a video-like reproduction of user interactions, including console logs and network activity) from the specified project and organization. |
| `SENTRY_DELETE_PROJECT_RULE` | Delete project rule | Permanently deletes a specific issue alert rule from an existing project within an existing Sentry organization. |
| `SENTRY_DELETE_PROJECT_TEAM_ASSOCIATION` | Delete project team association | Revokes a team's access to a Sentry project; this operation is idempotent. |
| `SENTRY_DELETE_RELEASE_FILE_BY_ID` | Delete release file by id | Permanently deletes a specific build artifact (e.g., source map, application bundle) associated with a project release. |
| `SENTRY_DELETE_SYMBOL_SOURCE_FROM_PROJECT` | Delete a symbol source from a project | Deletes a custom symbol source from a Sentry project. Use when you need to remove a symbol source that is no longer needed or needs to be reconfigured. |
| `SENTRY_DELETE_TEAM_BY_ORGANIZATION_OR_TEAM_SLUG` | Delete team by organization and team slug | Schedules a Sentry team for asynchronous deletion, which releases the team's slug for reuse upon successful scheduling. |
| `SENTRY_DELETE_TEAM_FROM_ORG_SCIM_V2` | Delete a team from an organization (SCIM v2) | Permanently and irreversibly deletes a specific team from a Sentry organization via a SCIM v2 request, provided SCIM integration is enabled for the organization. |
| `SENTRY_DELETE_USER_EMAILS_BY_ID` | Delete user emails by id | Permanently removes a Sentry user's email address; if multiple emails exist, Sentry's API logic (e.g., primary or previously marked) determines which is deleted. |
| `SENTRY_DELETE_USER_FROM_ORG` | Delete user from org | Removes a SCIM-managed member from a Sentry organization that has SCIM enabled, permanently revoking their access. |
| `SENTRY_DISABLE_SPIKE_PROTECTION` | Disable spike protection | Disables Spike Protection feature for specified projects within a Sentry organization. Use this when you need to turn off spike protection for one or more projects. |
| `SENTRY_FETCH_ALERTS` | Fetch alerts | Retrieves a list of alerts (workflows) for a Sentry organization. Use to get alert configurations, statuses, and trigger details. ⚠️ Note: This endpoint is currently in beta and may be subject to change. It is supported by New Monitors and Alerts and may not be viewable in the UI today. |
| `SENTRY_FETCH_A_MONITOR` | Fetch a monitor | Fetches detailed information for a specific monitor (detector) within an organization. Use when you need to retrieve monitor configuration, status, or settings. This endpoint is currently in beta and is supported by New Monitors and Alerts. |
| `SENTRY_FETCH_AN_ALERT` | Fetch an alert | Retrieves detailed information for a specific alert workflow. Use when you need to get alert configuration, triggers, action filters, or monitoring status. This endpoint is currently in beta and supported by New Monitors and Alerts. |
| `SENTRY_FETCH_AN_ORGANIZATIONS_MONITORS` | Fetch an organization's monitors | Retrieves monitors (detectors) for a Sentry organization. This endpoint is currently in beta and may be subject to change. Use when you need to list or query monitors for an organization. |
| `SENTRY_FETCH_ISSUE_EVENT_BY_ID` | Fetch issue event by id | Retrieves the 'latest', 'oldest', or 'recommended' event for a Sentry issue within an organization, optionally filtered by environment(s). |
| `SENTRY_FETCH_ORGANIZATION_ALERT_RULES` | Fetch organization alert rules | Retrieves a list of active metric alert rules for an existing Sentry organization, identified by its ID or slug. Note: This endpoint returns metric alert rules only. If no metric alert rules exist for the organization, the API may return a 404 response which is handled gracefully by returning an empty list. For issue alert rules, use the project-level rules endpoint instead. |
| `SENTRY_FETCH_ORGANIZATION_RELEASE_THRESHOLD_STATUSES` | Fetch organization release threshold statuses | Retrieves derived health statuses for release thresholds in a Sentry organization for a given time range, optionally filtered by environment, project, or release; `start` and `end` times must be provided together. **`[WARNING]`**: This API is experimental (Alpha) and subject to change! |
| `SENTRY_FETCH_ORGANIZATION_REPLAY_COUNT` | Fetch organization replay count | Retrieves the total count of session replays for a specified Sentry organization, filterable by time range, environment, project, and query. |
| `SENTRY_FETCH_ORGANIZATION_REPLAY_DETAILS` | Fetch organization replay details | Retrieves detailed information for a specific replay session by ID within a Sentry organization, optionally filtering time-series data using `statsPeriod` or `start`/`end`, and further refining by projects, environments, or specific fields. |
| `SENTRY_FETCH_ORGANIZATION_REPLAY_SELECTORS` | Fetch organization replay selectors | Retrieves replay selectors (CSS/DOM selectors from session replays) for a Sentry organization. Selectors include elements with dead clicks or rage clicks, useful for identifying UI issues. Returns selector details with click counts and associated project IDs. Use `statsPeriod` for time filtering (preferred over start/end). |
| `SENTRY_FETCH_PROJECT_ENVIRONMENT_DETAILS` | Fetch project environment details | Retrieves detailed information for a specific environment within a Sentry project. |
| `SENTRY_FETCH_PROJECT_OWNERSHIP_DETAILS` | Fetch project ownership details | Retrieves the ownership configuration, like CODEOWNERS rules or Issue Owner settings, for a specified Sentry project. |
| `SENTRY_FETCH_PROJECT_RELEASE_FILES` | Fetch project release files | Retrieves artifact files (e.g., source maps, debug information files) for a specific release version in a Sentry project; requires existing organization, project, and release version with associated files. |
| `SENTRY_FETCH_PROJECT_REPLAY_CLICKS` | Fetch project replay clicks | Fetches a list of user click interactions for a specific Sentry session replay, including the clicked DOM element ID and timestamp. |
| `SENTRY_FETCH_REPLAY_RECORDING_SEGMENT` | Fetch replay recording segment | Retrieves a specific recording segment for a Sentry replay, requiring valid organization, project, replay, and segment identifiers. |
| `SENTRY_FETCH_TAG_VALUES_FOR_ISSUE` | Fetch Tag Values for Issue | Retrieves a list of distinct values for a specified tag key associated with an existing Sentry issue, useful for understanding tag manifestations like browser versions or affected users. |
| `SENTRY_GET_ALERTS` | Get alerts and monitors | Tool to retrieve all combined alert rules and monitors for a Sentry organization. Use when you need to get a unified view of both alert rules and cron monitors. This endpoint combines results from multiple sources into a single response. |
| `SENTRY_GET_INTEGRATION_DETAILS_BY_ORG` | Get integration details by org | Retrieves details for a specific integration, identified by `integration_id`, installed within an existing Sentry organization, identified by `organization_id_or_slug`. |
| `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` | Get organization by id or slug | Retrieves a Sentry organization by its ID or slug; use the `detailed` parameter to optionally exclude project and team details for a more concise response. |
| `SENTRY_GET_ORGANIZATION_DETAILS` | Get organization details | Retrieves Sentry organizations accessible via the current authentication, with scope varying between user (all in region) and API key (linked org only) credentials. |
| `SENTRY_GET_ORGANIZATION_ENVIRONMENTS` | Get organization environments | Lists deployment environments for a Sentry organization, optionally filtered by visibility status. Environments represent deployment contexts like 'production', 'staging', or 'development' where events are tracked. By default, only visible environments are returned. Use the visibility parameter to include hidden environments or view only hidden ones. |
| `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` | Get organization issue details | Retrieves detailed information for a specific issue within a Sentry organization. Accepts both numeric issue IDs (e.g., '7159174717') and short IDs displayed in the Sentry UI (e.g., 'PROJECT-123', 'SENTRY-4V'). Short IDs are automatically resolved to numeric IDs before fetching issue details. |
| `SENTRY_GET_ORGANIZATION_RELEASE_VERSION` | Get organization release version | Retrieves detailed information, including optional health data and statistics, for a specific release version within a Sentry organization. |
| `SENTRY_GET_ORGANIZATION_SESSIONS` | Get organization sessions | Retrieves time series data for an organization's Sentry project release health sessions; note session duration data (e.g., using `avg(session.duration)`) may be incomplete after Jan 12, 2023, results are capped at 10,000 data points, `statsPeriod` overrides `start`/`end` timestamps, and the `interval` parameter (default/min '1h', max '1d', format like `statsPeriod`) dictates time series resolution and must cleanly divide one day. |
| `SENTRY_GET_ORGANIZATION_STATS_SUMMARY` | Get organization stats summary | Retrieves summarized event statistics for a Sentry organization, aggregated by project, allowing queries for event counts or unique occurrences over a specified time period and resolution, with filtering by project, category, and outcome. |
| `SENTRY_GET_PROJECT_EVENTS` | Get project events | Retrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level. |
| `SENTRY_GET_PROJECT_EVENT_STATS` | Get project event stats | Retrieves time-series event statistics for a Sentry project. Returns an array of [timestamp, count] data points showing event volumes over time. Use this to analyze event trends, monitor error rates, or generate custom dashboards. The endpoint supports different event types (received, rejected, blacklisted, generated) and time resolutions (10s, 1h, 1d). **Important**: This endpoint may change in the future without notice. Monitor Sentry's API changelog for updates. **Common use cases**: - Monitor error rates over time - Analyze event rejection patterns - Generate custom analytics dashboards - Track event volume trends |
| `SENTRY_GET_PROJECT_HOOK` | Get project hook | Retrieves detailed information for an existing service hook within a Sentry project. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry, such as when alerts are triggered ('event.alert') or new events are processed ('event.created'). This action requires: - Authentication with 'project:read' scope - The hook_id (GUID) of an existing service hook, typically obtained from creating a hook or listing project hooks Common use cases: - Verifying hook configuration and status - Retrieving the webhook URL and secret for external system setup - Checking which events the hook is subscribed to - Auditing hook creation timestamps Note: The 'servicehooks' feature must be enabled on your Sentry plan to create or manage hooks, though reading existing hook details may be possible depending on your API permissions. |
| `SENTRY_GET_PROJECT_LIST` | Get project list | Lists all Sentry projects the authenticated token has membership access to across all organizations. IMPORTANT: This endpoint returns projects where the token's user is a member. An empty result does NOT mean no projects exist - it means the token lacks project membership. This commonly happens when: - The auth token has organization-level access but not explicit project membership - Projects exist in organizations you can access, but you're not a project member If you receive an empty list but know projects exist, use SENTRY_RETRIEVE_ORGANIZATION_PROJECTS instead, which lists all projects within a specific organization (requires organization_id_or_slug parameter). |
| `SENTRY_GET_PROJECT_MONITOR_BY_ID` | Get project monitor by id | Retrieves detailed information for a specific Sentry cron monitor, provided the organization, project, and monitor exist. |
| `SENTRY_GET_PROJECT_RULE_DETAILS` | Get project rule details | Retrieves detailed information for a specific issue alert rule within a Sentry project. |
| `SENTRY_GET_SCIM_GROUP_BY_TEAM_ID` | Get SCIM group by team ID | Retrieves SCIM group information for a specific Sentry team. Returns the team's SCIM representation including ID, display name, and member list (limited to 10,000 members). Requires SCIM to be enabled for the organization (Business Plan with SAML2). Use this to query team details via the SCIM protocol for identity provider integrations. |
| `SENTRY_GET_SENTRY_APP_INSTALLATIONS_FOR_ORGANIZATION` | Get sentry app installations for organization | Retrieves a list of Sentry App installations for a given organization, which must exist. |
| `SENTRY_GET_TEAM_MEMBERS_BY_ID_OR_SLUG` | Get team members by id or slug | Retrieves all active members of a Sentry team with detailed user information, roles, and permissions. This endpoint returns members who have accepted their team invitation. Users with pending invitations are excluded from the results. Each member object includes comprehensive details such as user profile information, organization and team roles, authentication status, and membership flags. |
| `SENTRY_GET_WHO_VIEWED_REPLAY_BY_PROJECT` | Get who viewed replay by project | Retrieves users who viewed a specific, existing session replay within a Sentry project and organization. |
| `SENTRY_INGEST_EVENT_VIA_DSN` | Ingest event via DSN | Ingests a single custom event into a Sentry project using its DSN via the Envelope ingestion endpoint. This may create or update an issue group depending on Sentry's grouping algorithm. Note: Sentry does not provide a direct API to 'create an issue group'; issues are created from ingested events. This tool allows controlled generation of events for testing or workflows requiring synthetic events. |
| `SENTRY_LIST_AN_ORGANIZATION_S_CLIENT_KEYS` | List an organization's client keys | Lists all client keys (DSNs) across all projects in an organization. Use when you need to audit keys organization-wide or filter keys by team or status. |
| `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` | List an organization's issues | Returns a list of issues (error groups) for an organization. Use when you need to retrieve and analyze error patterns, track unresolved issues, or monitor issue trends. Default query applies 'is:unresolved issue.priority:[high,medium]'. |
| `SENTRY_LIST_A_PROJECTS_USER_FEEDBACK` | List a project's user feedback | Retrieves a list of legacy user feedback items within a Sentry project. Use when you need to see user-reported feedback on errors. Note: This returns legacy User Reports, not submissions from the User Feedback Widget. |
| `SENTRY_LIST_A_TAGS_VALUES_FOR_AN_ISSUE` | List a tag's values for an issue | Returns a list of values associated with this key for an issue. Use when you need to analyze tag values, their frequency, or timeline for specific issue tags. |
| `SENTRY_LIST_ORGANIZATION_DASHBOARDS` | List organization dashboards | Retrieves a list of custom dashboards for a Sentry organization, with pagination support. |
| `SENTRY_LIST_ORGANIZATION_MEMBERS` | List organization members | Lists all members, including those with pending invitations, for a Sentry organization. |
| `SENTRY_LIST_ORGANIZATION_RELEASES` | List organization releases | Retrieves a list of releases for an existing Sentry organization, optionally filtering by a query string that matches the start of the release version. |
| `SENTRY_LIST_ORGANIZATION_REPOSITORIES` | List organization repositories | Retrieves a list of version control repositories for a specific Sentry organization, which must exist and is identified by its ID or slug. |
| `SENTRY_LIST_ORGANIZATION_USER_TEAMS` | List User's Teams in Organization | Retrieves a list of all teams that the authenticated user has access to within the specified Sentry organization. |
| `SENTRY_LIST_PROJECT_USERS` | List project users | Retrieves users who have interacted with or are recognized within a specific Sentry project, optionally filtered by a query. |
| `SENTRY_LIST_SCIM_V2_ORGANIZATION_USERS` | List SCIM v2 organization users | Retrieves a paginated list of SCIM (System for Cross-domain Identity Management) users for a Sentry organization, allowing for filtering, pagination, and attribute exclusion. |
| `SENTRY_LIST_SEER_AI_MODELS` | List Seer AI models | Retrieves the list of AI models currently used in production in Seer. Use when you need to discover which LLM models Seer is actively using. |
| `SENTRY_LIST_TEAMS_IN_ORGANIZATION` | List teams in organization | Lists teams for an existing Sentry organization, optionally including project details and supporting pagination via a cursor. |
| `SENTRY_MANAGE_TEAM_EXTERNAL_INTEGRATIONS` | Create an external team | Links an external team or channel (e.g., Slack, GitHub) to an existing Sentry team, using a pre-configured integration for the specified provider and its valid Sentry integration ID. |
| `SENTRY_MODIFY_ORGANIZATION_NOTIFICATION_ACTION` | Modify organization notification action | Modifies an organization's notification action, specifically for `spike-protection` triggers. |
| `SENTRY_MODIFY_ORGANIZATION_SETTINGS` | Modify organization settings | Updates settings for a Sentry organization, such as name, slug, member roles, privacy, and integrations; if `avatarType` is 'upload', `avatar` (base64 image) is required. |
| `SENTRY_MODIFY_RELEASE_FILE_ATTRIBUTES` | Modify release file attributes | Updates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file ID. |
| `SENTRY_MUTATE_AN_ORGANIZATION_S_ALERTS` | Mutate an organization's alerts | Bulk enable or disable alerts for an organization. Use when you need to activate or deactivate multiple alerts at once. This endpoint is in beta and may change in the future. |
| `SENTRY_MUTATE_AN_ORGANIZATIONS_MONITORS` | Mutate an organization's monitors | Bulk enable or disable monitors for an organization. This endpoint is in beta and may change. Use when you need to enable or disable multiple monitors at once based on filters. |
| `SENTRY_PATCH_SCIM_GROUP_OPERATIONS` | Patch SCIM group operations | Performs SCIM PATCH operations (RFC 7644) to update attributes of a SCIM-enabled Sentry team, provided SCIM integration is active for the organization. |
| `SENTRY_PATCH_USER_ACTIVE_STATUS_IN_ORGANIZATION` | Deactivate an organization member | Deactivates and permanently deletes a Sentry organization member by using a SCIM PATCH operation to set their 'active' attribute to 'false'. |
| `SENTRY_POST_SPIKE_PROTECTION_FOR_ORGANIZATION` | Enable spike protection for an organization | Enables or updates Spike Protection for specified projects (or all projects using `['$all']`) within an existing Sentry organization, to which the projects must belong. |
| `SENTRY_QUERY_EXPLORE_EVENTS_IN_TIMESERIES_FORMAT` | Query explore events in timeseries format | Retrieves explore data for a given organization as a timeseries. Use this to query timeseries data for 1 or many axis, with results optionally grouped by top events depending on parameters. |
| `SENTRY_RETRIEVE_A_CUSTOM_INTEGRATION_BY_ID_OR_SLUG` | Retrieve a custom integration by id or slug | Retrieves detailed information about a custom integration (Sentry App) by its slug. Use this action when you need to: - Get configuration details of a custom integration including scopes, webhooks, and OAuth settings - Check the status and permissions of an integration - Retrieve integration metadata such as name, description, and avatar - Verify which events an integration subscribes to Note: Provide the integration's slug (case-sensitive), not its UUID. |
| `SENTRY_RETRIEVE_AGGREGATED_TEST_RESULT_METRICS` | Retrieve aggregated test result metrics | Retrieves aggregated test result metrics for a repository, owner, and organization. Use when you need to analyze test performance and reliability metrics for a specific repository. |
| `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` | Retrieve alert rule details | Retrieves detailed information for a specific metric alert rule within a Sentry organization. Note: This endpoint is specifically for metric alert rules (organization-level alerts based on metrics like error count, latency, failure rate, etc.). For issue alert rules (project-level alerts triggered by events), use the project rules endpoint instead. The API may return 404 if: - The alert rule ID does not exist - The organization does not have metric alerts enabled - The organization does not exist or you don't have access |
| `SENTRY_RETRIEVE_A_MONITOR` | Retrieve a monitor | Retrieves detailed information for a specific monitor within an organization. Use when you need to check monitor configuration, status, schedule, environments, or alert settings. |
| `SENTRY_RETRIEVE_COMMIT_FILES_FOR_RELEASE` | Retrieve commit files for release | Retrieves files changed in commits for a specified Sentry release; the release must exist and have linked commits. |
| `SENTRY_RETRIEVE_COMMITS_FOR_ORGANIZATION_REPO` | Retrieve an organization's repository commits | Retrieves a list of commits for a given repository within a Sentry organization. |
| `SENTRY_RETRIEVE_CUSTOM_INTEG_ISSUE_LINKS_GIVEN_SENTRY_ISSUE` | Retrieve custom integration issue links | Retrieves all external issue links for a Sentry issue. Returns connections between the Sentry issue and external tracking systems (e.g., Jira, GitHub Issues, Linear, GitLab, Asana) created through custom integrations or Sentry Apps. Use this to see what external tickets or issues are linked to a Sentry error. |
| `SENTRY_RETRIEVE_DATA_FORWARDERS_FOR_AN_ORGANIZATION` | Retrieve data forwarders for an organization | Returns a list of data forwarders for an organization. Use when you need to retrieve all data forwarders configured for a specific organization. |
| `SENTRY_RETRIEVE_DSYM_FILES_FOR_PROJECT` | Retrieve dsym files for project | Retrieve a list of debug information files (dSYM files) for a specified Sentry project, used for symbolication to display human-readable stack traces. |
| `SENTRY_RETRIEVE_EVENT_ID_FOR_ORGANIZATION` | Retrieve event id for organization | Resolves a Sentry event ID to its project and issue details within an accessible Sentry organization. |
| `SENTRY_RETRIEVE_FILES_FOR_RELEASE` | Retrieve files for release | Retrieves artifact files for a specific release version in a Sentry organization; the organization and release must exist, and the response `data` field will contain the file information as a dictionary. |
| `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` | Retrieve issue events by id | Retrieves events for a specified Sentry `issue_id`, which must be an existing issue. |
| `SENTRY_RETRIEVE_ISSUE_HASHES_FOR_ORGANIZATION` | Retrieve issue hashes for organization | Retrieves a list of grouping checksums (hashes) generated by Sentry for a specific issue within an organization, used for understanding event aggregation. |
| `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` | Retrieve issue tag details | Retrieves detailed information (e.g., top values, counts) for a specific tag key on an existing Sentry issue; results are paginated (max 1000 values per page). |
| `SENTRY_RETRIEVE_MONITOR_CHECKINS` | Retrieve monitor checkins | Retrieves the history of check-ins for a Sentry monitor, providing insights into the health and performance of associated scheduled tasks. |
| `SENTRY_RETRIEVE_MONITOR_CHECKINS_BY_ORG` | Retrieve monitor checkins by org | Retrieves check-ins (pings/heartbeats of a monitored cron job or task) for a specific monitor within a Sentry organization. |
| `SENTRY_RETRIEVE_NOTIFICATION_ACTION_BY_ORG_ID` | Retrieve notification action by org id | Retrieves details for a specific Spike Protection Notification Action, which defines alerts for triggered spike protection rules, within a Sentry organization. |
| `SENTRY_RETRIEVE_ORGANIZATION_DASHBOARD` | Retrieve organization dashboard | Fetches detailed information about a specific custom dashboard within a Sentry organization. |
| `SENTRY_RETRIEVE_ORGANIZATION_EVENTS` | Retrieve organization events | Retrieves Discover event data for a Sentry organization; the `sort` field must be in the `field` list (not an equation), and `field` has a 20-item limit. |
| `SENTRY_RETRIEVE_ORGANIZATION_INTEGRATIONS_LIST` | Retrieve organization integrations list | Retrieves a list of available integrations for an existing Sentry organization. |
| `SENTRY_RETRIEVE_ORGANIZATION_MEMBER` | Retrieve organization member | Retrieves details for a Sentry organization member or pending invitee, including role, teams, and status, using their member ID and the organization's ID or slug. |
| `SENTRY_RETRIEVE_ORGANIZATION_MONITORS` | Retrieve organization monitors | Retrieves cron monitors for a Sentry organization, including details of nested monitor environments. |
| `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` | Retrieve organization projects | Retrieves a list of Sentry projects for a specified organization (which must be accessible), supporting pagination via cursor. Note: The {region} placeholder in the base URL is handled by the OpenAPIAction framework, which overrides it with the base_url from auth metadata (typically 'https://sentry.io'). This ensures correct URL construction regardless of the region placeholder in the template. |
| `SENTRY_RETRIEVE_ORGANIZATION_RELAY_USAGE` | Retrieve organization relay usage | Retrieves a list of trusted Sentry Relays configured for an organization. Sentry Relay is a service that proxies events between your application and Sentry. This endpoint returns the configuration of trusted relays registered for an organization. Each trusted relay entry includes details such as the relay name, public key for authentication, and a description of its purpose. Note: This feature is typically available for organizations on Business and Enterprise plans that have Relay infrastructure enabled. Organizations without any configured relays will return an empty list. Use this to: - View all trusted relays configured for your organization - Verify relay configurations and public keys - Audit relay infrastructure setup |
| `SENTRY_RETRIEVE_ORGANIZATION_RELEASE_COMMITS` | Retrieve organization release commits | Retrieves a list of commits for a given release version in an existing Sentry organization, if the release exists. |
| `SENTRY_RETRIEVE_ORGANIZATION_REPLAYS` | Retrieve organization replays | Fetches session replays for a Sentry organization; use `statsPeriod` for relative time, or `start` and `end` (used together) for absolute time ranges. |
| `SENTRY_RETRIEVE_ORGANIZATION_SCIM_GROUPS` | Retrieve organization SCIM groups | Retrieves a paginated list of SCIM groups (teams) for a Sentry organization; the `members` field in the response for each group will contain at most 10,000 members. |
| `SENTRY_RETRIEVE_ORGANIZATION_STATS_V2` | Retrieve organization stats v2 | Retrieves Sentry organization event statistics; specify time range with `statsPeriod` OR both `start`/`end`; note that grouping by `project` returns a sum not a time-series, and `interval` (if used) must be 1h-1d and cleanly divide 24 hours. |
| `SENTRY_RETRIEVE_ORG_INTEGRATION_CONFIG` | Retrieve org integration config | Retrieves configuration for all integrations, or a specific integration if `providerKey` is given, for an existing Sentry organization. |
| `SENTRY_RETRIEVE_PAGINATED_REPOSITORY_TOKENS` | Retrieve paginated repository tokens | Retrieves a paginated list of repository tokens for a given owner. Use when you need to access repository tokens with pagination support. |
| `SENTRY_RETRIEVE_PROJECT_ENVIRONMENTS` | Retrieve project environments | Retrieves a list of environments for an existing project within a Sentry organization. |
| `SENTRY_RETRIEVE_PROJECT_EVENT_BY_ID` | Retrieve project event by id | Retrieves detailed information for a specific Sentry event using its ID, organization identifier, and project identifier. |
| `SENTRY_RETRIEVE_PROJECT_FILTER_DATA` | Retrieve project filter data | Retrieves a Sentry project's current data filtering settings, used to ignore events from sources like localhost, web crawlers, or legacy browsers. |
| `SENTRY_RETRIEVE_PROJECT_HOOKS` | Retrieve project hooks | Return a list of service hooks (webhooks) bound to a Sentry project, used to send notifications to external services upon event occurrences. |
| `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` | Retrieve project issues list | Retrieves a list of issues for a Sentry project, defaulting to unresolved issues unless an empty `query` string is provided or specific `hashes` are used. |
| `SENTRY_RETRIEVE_PROJECT_KEY_DETAILS` | Retrieve project key details | Retrieves details of a specific client key (DSN) for a Sentry project, which is used by Sentry SDKs to send event data. |
| `SENTRY_RETRIEVE_PROJECT_KEYS_BY_ORG_AND_PROJECT` | List a project's client keys | Retrieves a list of client keys (DSNs), used by Sentry SDKs to send events, for a specified project within an organization. |
| `SENTRY_RETRIEVE_PROJECT_MEMBERS_LIST` | Retrieve project members list | Retrieves active organization members belonging to any team assigned to the specified Sentry project. |
| `SENTRY_RETRIEVE_PROJECT_RELEASE_FILE_DETAILS` | Retrieve project release file details | Retrieves metadata (default) or raw content (if `download` is true) for a specific file within a Sentry project's release version. |
| `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` | Retrieve project rules by org and project id | Retrieves a list of active issue alert rules associated with a specific project within an organization. Returns all active issue alert rules configured for the specified project, including their conditions, filters, actions, and metadata. This endpoint is useful for auditing alert configurations, managing alert rules programmatically, or understanding what alerts are active in a project. |
| `SENTRY_RETRIEVE_PROJECT_SYMBOL_SOURCES` | Retrieve project symbol sources | Retrieves custom symbol sources for a Sentry project, either listing all or fetching a specific one if its ID is provided. |
| `SENTRY_RETRIEVE_PROJECT_TAG_VALUES` | Retrieve project tag values | Retrieves up to 1000 unique values for a specified tag key that has been recorded for events within a Sentry project. Returns an empty list if the tag key doesn't exist or has no values recorded yet. |
| `SENTRY_RETRIEVE_PROJECT_TEAMS` | Retrieve project teams | Retrieves a list of teams with explicit access to a specific project within a Sentry organization. |
| `SENTRY_RETRIEVE_RELEASE_COMMITS` | Retrieve release commits | Retrieves a list of commits associated with a specific release version within a Sentry project. |
| `SENTRY_RETRIEVE_RELEASE_DEPLOYMENTS` | Retrieve release deployments | Retrieves a list of all deployment records for a specific release version in an organization, detailing each deployment's environment and timestamps. |
| `SENTRY_RETRIEVE_RELEASE_FILE_BY_ID` | Retrieve release file by id | Retrieves a specific file's content or its metadata from a Sentry release, using the `download` parameter to choose between raw content or JSON metadata. |
| `SENTRY_RETRIEVE_REPLAY_RECORDING_SEGMENTS` | Retrieve replay recording segments | Retrieves a paginated list of recording segments for a specific Sentry replay, used for reconstructing or analyzing the replay. |
| `SENTRY_RETRIEVE_SAVED_DISCOVER_QUERIES` | Retrieve saved discover queries | Retrieves a paginated list of saved Discover queries for a Sentry organization. Returns saved query definitions that can be used to reproduce specific event searches and analyses. Supports filtering by name and sorting by various criteria (name, date, popularity, etc.). **Important**: This endpoint may return 404 if the Discover saved queries feature has been deprecated for the organization (organizations with 'discover-saved-queries-deprecation' feature flag). In such cases, the action gracefully returns an empty list with an explanatory message instead of failing. Organizations migrating to newer query systems may have this feature disabled. |
| `SENTRY_RETRIEVE_SAVED_DISCOVER_QUERY_FOR_ORGANIZATION` | Retrieve saved discover query for organization | Retrieves a specific saved Discover query (a predefined set of filters and conditions for exploring event data) for a Sentry organization. |
| `SENTRY_RETRIEVE_SEER_ISSUE_FIX_STATE` | Retrieve Seer issue fix state | Retrieves the current detailed state of an AI-assisted autofix process for a Sentry issue. Use when you need to check the progress, status, root cause analysis, proposed solutions, or code modifications for an autofix operation. |
| `SENTRY_RETRIEVE_SHORT_ID_FOR_ORGANIZATION` | Retrieve short id for organization | Resolves a Sentry short ID (e.g., 'PROJECT-1A') to its complete issue details including organization slug, project slug, group ID, and full issue metadata. Use this to look up issue information when you have a short ID reference. |
| `SENTRY_RETRIEVE_SOURCE_MAP_DEBUG_EVENT` | Retrieve source map debug event | Retrieves detailed debug information for diagnosing source map processing issues for a specific Sentry event, stack trace frame, and exception index. Note: The event must contain an exception with stack trace frames for this endpoint to return useful data. |
| `SENTRY_RETRIEVE_TEAM_INFO_VIA_ORGANIZATION_ID_OR_SLUG` | Retrieve team info | Retrieves detailed information for an existing Sentry team within its organization, optionally expanding related data (e.g., projects) or collapsing sections (e.g., organization details). |
| `SENTRY_RETRIEVE_TEAM_PROJECTS` | Retrieve team projects | Retrieves a list of Sentry projects for a specific team within an organization, supporting pagination via a cursor. |
| `SENTRY_RETRIEVE_THE_CUSTOM_INTEGS_CREATED_BY_AN_ORG` | Retrieve the custom integrations created by an organization | Retrieves custom integrations (Sentry Apps) created by an organization. Use when you need to list all custom integrations that the organization has developed. |
| `SENTRY_RETRIEVE_USER_EMAIL_INFORMATION` | Retrieve user email information | Retrieves a list of email addresses for an existing Sentry user, identified by their `user_id`. |
| `SENTRY_RETRIEVE_USER_VIA_SCIM_API` | Retrieve user via SCIM API | Retrieves an individual Sentry organization member's details using the SCIM v2 API. Returns a SCIM-formatted user resource containing the member's ID, username (email), email addresses, name (givenName and familyName), active status, and Sentry organization role. **Requirements**: This endpoint requires SCIM to be enabled for the organization, which requires a Business Plan subscription and SAML2 authentication enabled. A SCIM bearer token (not a regular API token) must be used for authentication. **Note**: Sentry's SCIM API does not support syncing passwords or setting user attributes other than 'active'. |
| `SENTRY_SAVE_ORGANIZATION_DISCOVER_QUERY` | Save organization discover query | Saves a new Discover query with a unique name for a Sentry organization, allowing reuse of search criteria for analyzing event data (errors, transactions) across specified projects and environments. |
| `SENTRY_START_SEER_ISSUE_FIX` | Start Seer issue fix | Trigger a Seer Issue Fix run for a specific issue. Use when you want to start an AI-assisted autofix process that operates asynchronously to identify root causes, propose solutions, generate code changes, and optionally create pull requests with fixes. |
| `SENTRY_SUBMIT_NOTIFICATION_ACTION_API_DATA` | Submit notification action API data | Creates a Sentry notification action for 'spike-protection' triggers, requiring `integration_id` if `service_type` is 'slack', 'pagerduty', or 'opsgenie', and `target_identifier`/`target_display` if `service_type` is 'slack' or 'opsgenie'. |
| `SENTRY_SWITCH_TEAM_ROLE_FOR_MEMBER` | Switch team role for member | Changes a member's role within a Sentry team, ensuring the member is already part of the team and that any organization-level role restrictions are respected. |
| `SENTRY_TOGGLE_PROJECT_FILTER_STATUS` | Toggle project filter status | Updates the status or configuration of a specific inbound data filter for a Sentry project; use `active` for most filters, or `subfilters` if `filter_id` is `legacy-browsers`. |
| `SENTRY_UPDATE_A_MONITOR` | Update a monitor | Updates a monitor's configuration and settings. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, or alert thresholds. |
| `SENTRY_UPDATE_A_MONITOR_BY_ID` | Update a monitor by ID | Updates an existing Sentry monitor (detector) for metric-based issue detection. Use when you need to modify monitor configuration, thresholds, data sources, or enable/disable the monitor. Note: This endpoint is in beta and may change. |
| `SENTRY_UPDATE_AN_ALERT_BY_ID` | Update an alert by ID | Tool to update an existing Sentry alert (workflow) by ID. Use when you need to modify alert settings like name, filters, triggers, or configuration. Note: This endpoint is in beta and supported by New Monitors and Alerts. |
| `SENTRY_UPDATE_AN_EXISTING_CUSTOM_INTEGRATION` | Update an existing custom integration | Updates an existing custom integration (Sentry App) with new configuration. Use this action to modify integration settings such as name, scopes, webhook URL, or other configuration. You must provide the integration's slug or ID and the required fields (name and scopes). |
| `SENTRY_UPDATE_A_PROJECTS_SYMBOL_SOURCE` | Update a symbol source in a project | Updates an existing custom symbol source (HTTP, GCS, or S3) in a project for fetching debug symbols. Use when you need to modify the configuration of a symbol source identified by its ID. |
| `SENTRY_UPDATE_ENVIRONMENT_VISIBILITY` | Update environment visibility | Updates the visibility of a specific environment within a Sentry project. |
| `SENTRY_UPDATE_EXTERNAL_TEAM_INTEGRATION` | Update external team integration | Updates an existing external team integration's display name, provider, Sentry integration ID, or external ID; the `integration_id` must match a valid, configured Sentry integration for the organization and the specified `provider`. |
| `SENTRY_UPDATE_EXTERNAL_USER_FOR_ORGANIZATION` | Update external user for organization | Updates attributes of an existing external user linkage (identified by `external_user_id`) within a Sentry organization (specified by `organization_id_or_slug`). |
| `SENTRY_UPDATE_ISSUE_ATTRIBUTES_IN_ORGANIZATION` | Update issue attributes in organization | Updates specified attributes of an existing Sentry issue within a Sentry organization, leaving other attributes unchanged. |
| `SENTRY_UPDATE_MONITOR_FOR_PROJECT` | Update monitor for project | Updates a monitor for a project. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, status, owner, or alert thresholds for a project-level monitor. |
| `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` | Update organization alert rules | Replaces an existing Sentry metric alert rule's configuration; fields not provided in the request are removed or reset. This action updates an existing metric alert rule. Note that this is a full replacement - any fields not provided will be removed or reset to defaults. Prerequisites: - The organization must have metric alerts feature enabled - The alert_rule_id must be a valid existing metric alert rule - Use SENTRY_FETCH_ORGANIZATION_ALERT_RULES to get existing alert rule IDs |
| `SENTRY_UPDATE_ORGANIZATION_DASHBOARD` | Update organization dashboard | Updates an existing custom dashboard, allowing modifications to its title, widgets, and data filters; providing `widgets`, `projects`, `environment`, `period`, `start`, `end`, or `filters` will overwrite existing settings for those fields. |
| `SENTRY_UPDATE_ORGANIZATION_MEMBER_ROLE` | Update organization member role | Updates a Sentry organization member's organization-level role (`orgRole`) and/or their team roles (`teamRoles`), ensuring the initiator has permissions equivalent to both the member's current and intended new `orgRole` if `orgRole` is being modified. |
| `SENTRY_UPDATE_PROJECT_DETAILS` | Update project details | Updates a Sentry project's settings (e.g., name, slug, platform, bookmark status); `isBookmarked` can be updated with `project:read` permission, other fields typically require `project:write` or `project:admin` permissions. |
| `SENTRY_UPDATE_PROJECT_ISSUE_STATUS_AND_DETAILS` | Update project issue status and details | Bulk update attributes of issues in a Sentry project, targeting issues by a list of IDs or by a query status (which implies updating all matching issues if IDs are omitted). |
| `SENTRY_UPDATE_PROJECT_KEY_CONFIGURATION` | Update project key configuration | Updates configuration settings (e.g., name, status, rate limits, SDK options) for an existing Sentry client key (DSN), identified by `key_id`, within a specified `project_id_or_slug` and `organization_id_or_slug`. |
| `SENTRY_UPDATE_PROJECT_OWNERSHIP_SETTINGS` | Update project ownership settings | Updates the ownership configuration settings (raw rules, fallthrough, auto-assignment, CODEOWNERS sync) for a Sentry project; omitted attributes retain their current values. |
| `SENTRY_UPDATE_PROJECT_RELEASE_FILE_DETAILS` | Update project release file details | Updates the name (path) or distribution identifier of a specific file within an existing project release in Sentry. |
| `SENTRY_UPDATE_PROJECT_RULE_BY_ID` | Update Project Rule By Id | Updates an existing Sentry project issue alert rule by `rule_id`, completely overwriting it; all rule fields must be provided in the request, as omitted fields may be cleared or reset to defaults. |
| `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` | Update release details for organization | Updates an existing Sentry release's details for an organization, including its reference, URL, release date, associated commits, or repository references. |
| `SENTRY_UPDATE_SAVED_QUERY_FOR_ORGANIZATION` | Update a saved query for an organization | Updates an existing Discover saved query for a Sentry organization. |
| `SENTRY_UPDATE_TEAM_INFORMATION_BY_ORGANIZATION_ID` | Update team information by organization id | Updates the slug for an existing team within a Sentry organization. |
| `SENTRY_UPDATE_USER_EMAIL` | Update user email | Updates the primary email address for a Sentry user. The new email must already be added as a secondary email and be verified. **AUTHENTICATION REQUIREMENTS:** - Requires `user:write` scope - Typically requires a PERSONAL auth token (created from User Settings > Personal Tokens) - Internal integration tokens (organization-scoped) may not have permission for user-level operations **PREREQUISITES:** - The new email must already be added to the user's account as a secondary email - The email must be verified before it can be set as primary **COMMON ERRORS:** - 403 Forbidden: Token lacks user:write scope or is not a personal auth token - 400 Bad Request: Email is not already added to the account or is not verified |
| `SENTRY_UPDATE_WEBHOOK_CONFIGURATION_XP` | Update webhook configuration | Updates an existing Sentry service hook's target URL and subscribed event types for a given project and organization. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry. This action allows you to modify the webhook's URL and change which events trigger notifications. Valid event types are: - 'event.alert': Triggered when alerts fire - 'event.created': Triggered when new events are processed Requirements: - Authentication with 'project:write' scope - The 'servicehooks' feature must be enabled for your Sentry plan - The hook_id must be a valid GUID from an existing service hook Common use cases: - Updating webhook URL when your endpoint changes - Modifying event subscriptions to receive different notification types - Reconfiguring webhooks for testing or production environments |
| `SENTRY_UPLOAD_DSYMS_FILE_TO_PROJECT` | Upload dsyms file to project | Uploads a dSYM (debug symbols) zip archive, containing an Apple .dSYM folder, to the specified Sentry project for symbolicating crash reports from Apple platforms. |
| `SENTRY_UPLOAD_FILE_TO_PROJECT_RELEASE` | Upload file to project release | Uploads a file to a Sentry project release, for an existing organization, project, and version; uses `multipart/form-data` and the region-specific Sentry domain. |
| `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` | Upload release file to organization | Uploads a new file, such as a source map or debug information, to an existing release version in a Sentry organization. |
| `SENTRY_VIEW_ORGANIZATION_NOTIFICATION_ACTIONS` | View organization notification actions | Retrieves Spike Protection notification actions for a Sentry organization, filterable by project IDs or slugs (slugs take precedence); if `triggerType` is used, it must be 'spike-protection'. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Sentry MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Sentry account. It provides structured and secure access so Claude can perform Sentry operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Sentry account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["sentry"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http sentry-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['sentry'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http sentry-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Sentry MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (sentry-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http sentry-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Sentry MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your sentry-composio entry in the list
- This confirms that Claude Code can now access Sentry tools
If everything is wired up, you should see your sentry-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Sentry

The first time you try to use Sentry tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Sentry
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Sentry authorization flow
- Return to the terminal and start using Sentry through Claude Code
Once authenticated, you can ask Claude Code to perform Sentry operations in natural language. For example:
- "Create dashboard tracking errors for my project"
- "Add new member to Sentry organization"
- "Set up alert for critical exceptions"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["sentry"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http sentry-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['sentry'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http sentry-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Sentry with Claude Code using Composio's MCP server. Now you can interact with Sentry directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Sentry operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Sentry operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Sentry MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/sentry/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/sentry/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/sentry/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/sentry/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/sentry/framework/codex)
- [Cursor](https://composio.dev/toolkits/sentry/framework/cursor)
- [VS Code](https://composio.dev/toolkits/sentry/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/sentry/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/sentry/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/sentry/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/sentry/framework/cli)
- [Google ADK](https://composio.dev/toolkits/sentry/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/sentry/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/sentry/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/sentry/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/sentry/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/sentry/framework/crew-ai)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Sentry MCP?

With a standalone Sentry MCP server, the agents and LLMs can only access a fixed set of Sentry tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Sentry and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Sentry tools.

### Can I manage the permissions and scopes for Sentry while using Tool Router?

Yes, absolutely. You can configure which Sentry scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Sentry data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)