Sentry Automation

1---
2name: sentry-automation
3description: "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."
4requires:
5  mcp: [rube]
6---
7 
8# Sentry Automation via Rube MCP
9 
10Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Sentry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17 
18## Setup
19 
20**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.
21 
22 
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`
253. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth
264. Confirm connection status shows ACTIVE before running any workflows
27 
28## Core Workflows
29 
30### 1. Investigate Issues
31 
32**When to use**: User wants to find, inspect, or triage error issues
33 
34**Tool sequence**:
351. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required]
362. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional]
373. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional]
384. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional]
395. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional]
40 
41**Key parameters**:
42- `organization_id_or_slug`: Organization identifier
43- `issue_id`: Numeric issue ID
44- `query`: Search query (e.g., `is:unresolved`, `assigned:me`, `browser:Chrome`)
45- `sort`: Sort order (`date`, `new`, `freq`, `priority`)
46- `statsPeriod`: Time window for stats (`24h`, `14d`, etc.)
47 
48**Pitfalls**:
49- `organization_id_or_slug` is the org slug (e.g., 'my-org'), not the display name
50- Issue IDs are numeric; do not confuse with event IDs which are UUIDs
51- Query syntax uses Sentry's search format: `is:unresolved`, `assigned:me`, `!has:release`
52- Events within an issue can have different stack traces; inspect individual events for details
53 
54### 2. Manage Project Issues
55 
56**When to use**: User wants to view issues scoped to a specific project
57 
58**Tool sequence**:
591. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - List projects to find project slug [Prerequisite]
602. `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` - List issues for a specific project [Required]
613. `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` - Get events for a specific issue [Optional]
62 
63**Key parameters**:
64- `organization_id_or_slug`: Organization identifier
65- `project_id_or_slug`: Project identifier
66- `query`: Search filter string
67- `statsPeriod`: Stats time window
68 
69**Pitfalls**:
70- Project slugs are different from project display names
71- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first
72- Project-scoped issue lists may have different pagination than org-scoped lists
73 
74### 3. Configure Alert Rules
75 
76**When to use**: User wants to create or manage alert rules for a project
77 
78**Tool sequence**:
791. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - Find project for the alert [Prerequisite]
802. `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` - List existing rules [Optional]
813. `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` - Create a new alert rule [Required]
824. `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` - Create org-level metric alert [Alternative]
835. `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` - Update existing alert rules [Optional]
846. `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` - Inspect specific alert rule [Optional]
857. `SENTRY_GET_PROJECT_RULE_DETAILS` - Get project-level rule details [Optional]
86 
87**Key parameters**:
88- `name`: Alert rule name
89- `conditions`: Array of trigger conditions
90- `actions`: Array of actions to perform when triggered
91- `filters`: Array of event filters
92- `frequency`: How often to trigger (in minutes)
93- `actionMatch`: 'all', 'any', or 'none' for condition matching
94 
95**Pitfalls**:
96- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different
97- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types
98- `frequency` is in minutes; setting too low causes alert fatigue
99- `actionMatch` defaults may vary; explicitly set to avoid unexpected behavior
100 
101### 4. Manage Releases
102 
103**When to use**: User wants to create, track, or manage release versions
104 
105**Tool sequence**:
1061. `SENTRY_LIST_ORGANIZATION_RELEASES` - List existing releases [Optional]
1072. `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` - Create a new release [Required]
1083. `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` - Update release metadata [Optional]
1094. `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` - Record a deployment for a release [Optional]
1105. `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` - Upload source maps or files [Optional]
111 
112**Key parameters**:
113- `version`: Release version string (e.g., '1.0.0', commit SHA)
114- `projects`: Array of project slugs this release belongs to
115- `dateReleased`: Release timestamp (ISO 8601)
116- `environment`: Deployment environment name (e.g., 'production', 'staging')
117 
118**Pitfalls**:
119- Release versions must be unique within an organization
120- Releases can span multiple projects; use the `projects` array
121- Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY
122- Source map uploads require the release to exist first
123 
124### 5. Monitor Organization and Teams
125 
126**When to use**: User wants to view org structure, teams, or member lists
127 
128**Tool sequence**:
1291. `SENTRY_GET_ORGANIZATION_DETAILS` or `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` - Get org info [Required]
1302. `SENTRY_LIST_TEAMS_IN_ORGANIZATION` - List all teams [Optional]
1313. `SENTRY_LIST_ORGANIZATION_MEMBERS` - List org members [Optional]
1324. `SENTRY_GET_PROJECT_LIST` - List all accessible projects [Optional]
133 
134**Key parameters**:
135- `organization_id_or_slug`: Organization identifier
136- `cursor`: Pagination cursor for large result sets
137 
138**Pitfalls**:
139- Organization slugs are URL-safe identifiers, not display names
140- Member lists may be paginated; follow cursor pagination
141- Team and member visibility depends on the authenticated user's permissions
142 
143### 6. Manage Monitors (Cron Monitoring)
144 
145**When to use**: User wants to update cron job monitoring configuration
146 
147**Tool sequence**:
1481. `SENTRY_UPDATE_A_MONITOR` - Update monitor configuration [Required]
149 
150**Key parameters**:
151- `organization_id_or_slug`: Organization identifier
152- `monitor_id_or_slug`: Monitor identifier
153- `name`: Monitor display name
154- `schedule`: Cron schedule expression or interval
155- `checkin_margin`: Grace period in minutes for late check-ins
156- `max_runtime`: Maximum expected runtime in minutes
157 
158**Pitfalls**:
159- Monitor slugs are auto-generated from the name; use slug for API calls
160- Schedule changes take effect immediately
161- Missing check-ins trigger alerts after the margin period
162 
163## Common Patterns
164 
165### ID Resolution
166 
167**Organization name -> Slug**:
168```
1691. Call SENTRY_GET_ORGANIZATION_DETAILS
1702. Extract slug field from response
171```
172 
173**Project name -> Slug**:
174```
1751. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
1762. Find project by name, extract slug
177```
178 
179### Pagination
180 
181- Sentry uses cursor-based pagination with `Link` headers
182- Check response for cursor values
183- Pass cursor in next request until no more pages
184 
185### Search Query Syntax
186 
187- `is:unresolved` - Unresolved issues
188- `is:resolved` - Resolved issues
189- `assigned:me` - Assigned to current user
190- `assigned:team-slug` - Assigned to a team
191- `!has:release` - Issues without a release
192- `first-release:1.0.0` - Issues first seen in release
193- `times-seen:>100` - Seen more than 100 times
194- `browser:Chrome` - Filter by browser tag
195 
196## Known Pitfalls
197 
198**ID Formats**:
199- Organization: use slug (e.g., 'my-org'), not display name
200- Project: use slug (e.g., 'my-project'), not display name
201- Issue IDs: numeric integers
202- Event IDs: UUIDs (32-char hex strings)
203 
204**Permissions**:
205- API token scopes must match the operations being performed
206- Organization-level operations require org-level permissions
207- Project-level operations require project access
208 
209**Rate Limits**:
210- Sentry enforces per-organization rate limits
211- Implement backoff on 429 responses
212- Bulk operations should be staggered
213 
214## Quick Reference
215 
216| Task | Tool Slug | Key Params |
217|------|-----------|------------|
218| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |
219| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |
220| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |
221| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |
222| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |
223| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |
224| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |
225| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |
226| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |
227| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |
228| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |
229| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |
230| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |
231| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |
232| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |
233