| 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. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | cloud-infrastructure |
| category | monitoring |
| risk | critical |
| source | community |
| tags | ["skill","cloud-infrastructure","monitoring","sentry","automation"] |
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.)
:
