sentry-automationlisted

# 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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry` 3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth 4. 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**: 1. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required] 2. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional] 3. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional] 4. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional] 5. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional] **Key parameters**: - `organization_id_or_slug`: Organization identifier - `issue_id`: Numeric i