# Sentry CLI for AI Agents

```json
{
  "title": "Sentry CLI for AI Agents",
  "toolkit": "Sentry",
  "toolkit_slug": "sentry",
  "framework": "CLI",
  "framework_slug": "cli",
  "url": "https://composio.dev/toolkits/sentry/framework/cli",
  "markdown_url": "https://composio.dev/toolkits/sentry/framework/cli.md",
  "updated_at": "2026-05-06T08:27:47.708Z"
}
```

## Introduction

CLIs are eating MCPs. The industry is converging on the very same idea. MCPs for all their merit can be token hungry, slow, and unreliable for complex tool chaining. However, coding agents have become incredibly good at working with CLIs, and in fact they are far more comfortable working with CLI tools than MCP.
With Composio's Universal CLI, your coding agents can talk to over 1000+ SaaS applications. With Sentry, agents can create dashboard tracking errors for your project, add new member to sentry organization, set up alert for critical exceptions, and more — all without worrying about authentication.
This guide walks you through Composio Universal CLI and explains how you can connect it with coding agents like Claude Code, Codex, OpenCode, etc, for end-to-end Sentry automation.

## 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 Code](https://composio.dev/toolkits/sentry/framework/claude-code)
- [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)
- [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

The idea behind building the universal CLI is to give agents a single command interface to interact with all your external applications. Here's what you'll get with it:
- Agent-friendly: Coding agents like Claude Code, Codex, and OpenCode can use CLI tools natively — no MCP setup required.
- Authentication handled: Connect once via OAuth or API Key, and all CLI commands work with your credentials automatically.
- Tool discovery: Search, inspect, and execute 20,000+ tools across 1000+ apps from one interface.
- Trigger support: Use triggers to listen for events across your apps, powered by real-time webhooks or polling under the hood.
- Type generation: Generate typed schemas for autocomplete and type safety in your projects.

## Connect Sentry to CLI

### Prerequisites
Install the Composio CLI, authenticate, and initialize your project:

```bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login
```

## 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_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_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' (preferred, as 'name' is deprecated) 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 where scim is enabled; a url-friendly slug is auto-generated from the `displayname` (e.g., 'my team' becomes 'my-team' by lowercasing and replacing spaces with dashes), and the team starts with no members. |
| `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_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 (e.g., from an sso provider) and a sentry user within the specified sentry organization. |
| `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 | Deletes a specific metric alert rule within a sentry organization. |
| `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. |
| `SENTRY_DELETE_ORGANIZATION_INTEGRATION` | Delete organization integration | Permanently deletes a specific integration previously installed for the sentry organization. |
| `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_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_SYMBOL_SOURCES` | Delete a project symbol source | Deletes a specific custom symbol source from a project. |
| `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` | Delete release file | Permanently deletes a specific file from an existing release, project, and organization; this action 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 release. |
| `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_FETCH_ISSUE_EVENT_BY_ID` | Fetch issue event by id | Retrieves the 'latest', 'oldest', or 'recommended' event for a sentry issue, 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. |
| `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 | Fetches replay selectors (css selectors for session replays) for a sentry organization, filterable by various criteria; use either `statsperiod` or `start`/`end` for time range, not both. |
| `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_GET_ACTIVATION_OF_ALERT_RULE_FOR_ORGANIZATION` | Get activation of alert rule for organization | Retrieves all activations (triggered instances) for a specific metric alert rule within a sentry organization. |
| `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 | Retrieves a list of deployment environments (e.g., 'production', 'staging') for a sentry organization, optionally filtering by visibility. |
| `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` | Get organization issue details | Retrieves detailed information for a specific issue within a sentry organization. |
| `SENTRY_GET_ORGANIZATION_MONITOR_BY_ID_OR_SLUG` | Get organization monitor by id or slug | Retrieves detailed information for a specific monitor (e.g., a cron job or scheduled task) within an organization. |
| `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 event statistics for a specified sentry project, returning data as [timestamp, count] pairs; ensure `since` precedes `until` if both are provided. |
| `SENTRY_GET_PROJECT_HOOK` | Get project hook | Retrieves detailed information for an existing service hook, identified by `hook id`, within a specific sentry project and organization. |
| `SENTRY_GET_PROJECT_LIST` | Get project list | Retrieves a list of sentry projects (representing monitored applications or services), useful for discovery or selecting a project for subsequent operations. |
| `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 sentry team, if scim is enabled for the organization; the 'members' list in the response is limited to 10,000 entries. |
| `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 a list of all active members for a sentry team, excluding users with pending invitations. |
| `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_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 organization user teams | 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_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_MONITOR_DATA` | Modify organization monitor data | Updates an existing sentry monitor's properties, requiring `name` and `type` (must be 'cron job'), and optionally `slug`, `status`, `owner`, or `is muted` state for a monitor within the specified organization. |
| `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_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_PROJECT_SYMBOL_SOURCES` | Add a symbol source to a project | Adds a new custom symbol source (http, gcs, or s3) to a project for fetching debug symbols; if an `id` is provided, it must be unique for the project and not start with 'sentry:'. |
| `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_RETRIEVE_ALERT_RULE_DETAILS` | Retrieve alert rule details | Retrieves detailed information for a specific metric alert rule within a sentry organization. |
| `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_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. |
| `SENTRY_RETRIEVE_ORGANIZATION_RELAY_USAGE` | Retrieve organization relay usage | Retrieves relay usage information, primarily a list of trusted relays, for a specified sentry organization, which must have relay usage enabled. |
| `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_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. |
| `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. |
| `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 list of saved discover queries for a sentry organization, optionally filtered and sorted. |
| `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_SHORT_ID_FOR_ORGANIZATION` | Retrieve short id for organization | Resolves an existing sentry short id to its issue details within a valid sentry organization. |
| `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. |
| `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_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_FEEDBACK_FOR_PROJECT` | Retrieve user feedback for project | Retrieves user feedback for a project from sentry's older 'user reports' system, excluding feedback from the modern 'user feedback widget'. |
| `SENTRY_RETRIEVE_USER_VIA_SCIM_API` | Retrieve user via SCIM API | Retrieves an individual sentry organization member's details accessible via scim v2 using their member id, noting that `firstname` and `lastname` in the response will be 'n/a'. |
| `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_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_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_SUBMIT_PROJECT_USER_FEEDBACK` | Submit project user feedback | Deprecated: submits user feedback for a sentry project event (use if newer sentry feedback tools are unavailable); submit within 30 mins of event, overwritable within 5 mins. |
| `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-browser`. |
| `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_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. |
| `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_MONITOR` | Update project monitor | Updates an existing sentry monitor (used for tracking recurring tasks/cron jobs) within a specific organization and project, allowing modification of its properties such as name, slug, type, status, owner, and muting status. |
| `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_SYMBOL_SOURCE_SETTINGS` | Update symbol source settings | Updates an existing custom symbol source's settings in a sentry project, such as its type, name, layout preferences, and connection parameters. |
| `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 for a sentry user; the new email must be valid and not already in use as a primary email by another sentry account. |
| `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. |
| `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.

## Complete Code

None listed.

## Conclusion

- Try asking your coding agent to perform various Sentry operations
- Explore cross-app workflows by connecting more toolkits
- Set up triggers for real-time automation
- Use composio generate for typed schemas in your projects

## 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 Code](https://composio.dev/toolkits/sentry/framework/claude-code)
- [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)
- [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 is the Composio Universal CLI?

The Composio Universal CLI is a single command-line interface that lets coding agents and developers interact with 1000+ SaaS applications. It handles authentication, tool discovery, action execution, and trigger setup — all from the terminal, without needing to configure MCP servers.

### Which coding agents work with the Composio CLI?

Any coding agent that can run shell commands works with the Composio CLI — including Claude Code, Codex, OpenCode, OpenClaw, and others. Once the CLI is installed, agents automatically discover and use the composio commands to interact with Sentry and other connected apps.

### How is the CLI different from using an MCP server for Sentry?

MCP servers require configuration and can be token-heavy for complex workflows. The CLI gives agents a direct, lightweight interface — no server setup needed. Agents simply call composio commands like any other shell tool. It's faster to set up, more reliable for multi-step tool chaining, and works natively with how coding agents already operate.

### How safe is my Sentry data when using the Composio CLI?

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. You can also bring your own OAuth credentials for full control.

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