Example routine
Weekly error trend review
Read Sentry issues and events to explain which errors are new, growing, or newly fixed.
Use this routineSuggested rhythm
Weekly
0 9 * * 1
America/Los_Angeles
Expected result
A weekly error brief separating new issues, regressions, and growth, linked to suspected releases with recommended owners.
Built for
Engineering · Support
Works with
- Sentry
What the routine does
Query approved Sentry tools for issues and events in the configured project over the reporting window. Compare against the prior period, separate new errors from regressions and growing existing issues, and connect spikes to recent releases where the data supports it. Recommend which issues deserve an owner this week and say why. Never modify or resolve issues unless that tool is explicitly approved.
Inputs
- Sentry project
{{project}}The Sentry project to review.
Example: acme-web
Required MCP capabilities
- Read Sentry issues
- Read Sentry events
Permission boundary
Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.