| name | sentry-automation |
| description | Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas. |
Sentry Automation via Rube MCP
Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Sentry connection via
RUBE_MANAGE_CONNECTIONS with toolkit sentry
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit sentry
- If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Investigate Issues
When to use: User wants to find, inspect, or triage error issues
Tool sequence:
SENTRY_LIST_AN_ORGANIZATIONS_ISSUES - List issues across the organization [Required]SENTRY_GET_ORGANIZATION_ISSUE_DETAILS - Get detailed info on a specific issue [Optional]SENTRY_LIST_AN_ISSUES_EVENTS - View individual error events for an issue [Optional]SENTRY_RETRIEVE_AN_ISSUE_EVENT - Get full event details with stack trace [Optional]SENTRY_RETRIEVE_ISSUE_TAG_DETAILS - Inspect tag distribution for an issue [Optional]
Key parameters:
organization_id_or_slug: Organization identifierissue_id: Numeric issue IDquery: Search query (e.g., is:unresolved, assigned:me, browser:Chrome)sort: Sort order (date, new, freq, priority)statsPeriod: Time window for stats (24h, 14d, etc.)
Pitfalls:
organization_id_or_slug is the org slug (e.g., 'my-org'), not the display name- Issue IDs are numeric; do not confuse with event IDs which are UUIDs
- Query syntax uses Sentry's search format:
is:unresolved, assigned:me, !has:release
- Events within an issue can have different stack traces; inspect individual events for details
2. Manage Project Issues
When to use: User wants to view issues scoped to a specific project
Tool sequence:
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS - List projects to find project slug [Prerequisite]SENTRY_RETRIEVE_PROJECT_ISSUES_LIST - List issues for a specific project [Required]SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID - Get events for a specific issue [Optional]
Key parameters:
organization_id_or_slug: Organization identifierproject_id_or_slug: Project identifierquery: Search filter stringstatsPeriod: Stats time window
Pitfalls:
- Project slugs are different from project display names
- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first
- Project-scoped issue lists may have different pagination than org-scoped lists
3. Configure Alert Rules
When to use: User wants to create or manage alert rules for a project
Tool sequence:
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS - Find project for the alert [Prerequisite]SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID - List existing rules [Optional]SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS - Create a new alert rule [Required]SENTRY_CREATE_ORGANIZATION_ALERT_RULE - Create org-level metric alert [Alternative]SENTRY_UPDATE_ORGANIZATION_ALERT_RULES - Update existing alert rules [Optional]SENTRY_RETRIEVE_ALERT_RULE_DETAILS - Inspect specific alert rule [Optional]SENTRY_GET_PROJECT_RULE_DETAILS - Get project-level rule details [Optional]
Key parameters:
name: Alert rule nameconditions: Array of trigger conditionsactions: Array of actions to perform when triggeredfilters: Array of event filtersfrequency: How often to trigger (in minutes)actionMatch: 'all', 'any', or 'none' for condition matching
Pitfalls:
- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different
- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types
frequency is in minutes; setting too low causes alert fatigueactionMatch defaults may vary; explicitly set to avoid unexpected behavior
4. Manage Releases
When to use: User wants to create, track, or manage release versions
Tool sequence:
SENTRY_LIST_ORGANIZATION_RELEASES - List existing releases [Optional]SENTRY_CREATE_RELEASE_FOR_ORGANIZATION - Create a new release [Required]SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION - Update release metadata [Optional]SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG - Record a deployment for a release [Optional]SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION - Upload source maps or files [Optional]
Key parameters:
version: Release version string (e.g., '1.0.0', commit SHA)projects: Array of project slugs this release belongs todateReleased: Release timestamp (ISO 8601)- `envi
