TL;DR
Error Alerting Pipeline is a monitoring workflow that chains Sentry + Slack to automate a common task. Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project. Once configured, it runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.
Error Alerting Pipeline
Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project.
How it works
Run with MCPizy
NewExecute this recipe in your browser — no local install, no Claude Code. Streams results live.
Why this combo?
Sentry captures errors with full stack traces and frequency data; Slack gets them to the right engineer immediately. Without this routing, errors pile up in a Sentry dashboard that nobody watches continuously. With it, new issues are impossible to miss and automatically assigned to the right team.
Without this workflow
Error occurs. Sits in Sentry unnoticed. User emails support. Support tickets engineer. Engineer opens Sentry. 6 hours pass.
With MCPizy
New error → enriched with commit author → routed to team channel → on-call mentioned → resolved in under 30 minutes.
Business value
Concrete ROI — not marketing fluff.
Time saved
- Deduplication prevents alert fatigue — on-call trusts the signal again, reducing burnout and attrition
Workflow steps
- 1Sentry webhook fires on new issue
- 2Enrich with last commit that touched the file
- 3Route to project-specific Slack channel
- 4Mention on-call engineer from PagerDuty
- 5Update thread with issue resolved event
Use cases
- Route frontend errors to #frontend-alerts, backend errors to #backend-alerts
- Enrich alerts with the git blame so the right developer is always pinged
- Thread-based updates so resolution is tracked in the same Slack conversation
- Deduplicate high-frequency errors so a single bad deploy doesn't spam the channel
Agent prompt (copy into Claude Code)
This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.
You are an error-alerting agent. Runs on Sentry webhooks (new issue, regression).
On issue.created or issue.unresolved:
1. Call sentry.get_issue(id) to fetch title, culprit (file+line), stacktrace, count, user_count
2. Call github.get_file_blame(repo, path=culprit.file, line=culprit.line) — extract last commit author + commit_sha
3. Build routing key: project tag (frontend|backend|mobile) → slack channel
4. De-dupe: skip if same issue posted in last 1 hour (check ~/.mcpizy/state/sentry-alerts.json)
5. Call slack.send_message(channel=routed_channel, blocks=[
header: :bug: ${issue.title},
section: culprit + users_affected + event_count,
context: ":bust_in_silhouette: owner: @${author}",
actions: [View in Sentry] [View commit ${sha[:7]}] [Ignore]
])
6. On issue.resolved, update the original thread with :white_check_mark:Trigger & credentials
How this workflow fires and what env vars you need.
POST /webhook/sentry (Sentry → Settings → Integrations → Webhooks, events: issue)
SENTRY_ORG_SLUGYour Sentry organization slug
e.g. acme
SLACK_FRONTEND_CHANNELChannel for frontend errors
e.g. #frontend-alerts
SLACK_BACKEND_CHANNELChannel for backend errors
e.g. #backend-alerts
One-command deploy
Install everything — MCPs, prompt, env template — in a single call.
$ mcpizy recipe install sentry-slack-error-alerting ✓ Installs all 2 MCP servers ✓ Writes prompt to ~/.mcpizy/prompts/sentry-slack-error-alerting.md ✓ Generates .env.example in current directory ✓ Ready to paste into Claude Code
Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.
Quick install (MCPs only)
$ mcpizy install sentry && mcpizy install slackMore Monitoring recipes
Database Change Alerts
Get a Slack alert whenever a critical Supabase table row is created, updated, or deleted — ideal for audit trails.
Database Monitoring Dashboard
Stream Postgres metrics — query latency, lock waits, vacuum stats — into Grafana for a live operations dashboard.
Alert Routing from Grafana
Grafana alerts are enriched with runbook links and routed to the correct Slack channel based on severity and team labels.
Analytics Dashboard
Connect ClickHouse to Grafana to build real-time analytics dashboards over billions of events with sub-second query times.
Frequently asked questions
What is this workflow?
Error Alerting Pipeline is a monitoring automation that uses Sentry + Slack together via the Model Context Protocol. Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project.
How long does setup take?
Setup takes around 8 min setup, zero missed errors. You install the required MCP servers with `mcpizy install sentry && mcpizy install slack`, connect your accounts, and the workflow is ready to run.
What does this workflow change in practice?
Deduplication prevents alert fatigue — on-call trusts the signal again, reducing burnout and attrition.
Which MCP servers do I need for this?
You need 2 MCP servers: Sentry (mcpizy install sentry), Slack (mcpizy install slack). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.
Does this work with Claude Code, Cursor, and Windsurf?
Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.
Start building this workflow
Install the required MCPs from the directory and automate this in 8 min setup.
$ mcpizy install sentry && mcpizy install slack
Free to install. Connect your accounts and this workflow runs itself.