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 saves ~6 hours/week per on-call engineer, plus recovery of users who would otherwise churn silently and runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.
Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project.
Execute this recipe in your browser — no local install, no Claude Code. Streams results live.
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.
Error occurs. Sits in Sentry unnoticed. User emails support. Support tickets engineer. Engineer opens Sentry. 6 hours pass.
New error → enriched with commit author → routed to team channel → on-call mentioned → resolved in under 30 minutes.
Concrete ROI — not marketing fluff.
Time saved
~6 hours/week per on-call engineer, plus recovery of users who would otherwise churn silently
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: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
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.
$ mcpizy install sentry && mcpizy install slackGet a Slack alert whenever a critical Supabase table row is created, updated, or deleted — ideal for audit trails.
Stream Postgres metrics — query latency, lock waits, vacuum stats — into Grafana for a live operations dashboard.
Grafana alerts are enriched with runbook links and routed to the correct Slack channel based on severity and team labels.
Connect ClickHouse to Grafana to build real-time analytics dashboards over billions of events with sub-second query times.
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.
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.
Once running, this workflow saves ~6 hours/week per on-call engineer, plus recovery of users who would otherwise churn silently. The concrete business value: Cuts mean time to detection from 6 hours to under 1 minute — catches silent user-impacting bugs before support tickets; Git-blame routing means the right person is pinged 90% of the time — no more 'who owns this?' Slack archaeology.
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`.
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.
Install the required MCPs from the marketplace and automate this in 8 min setup.
$ mcpizy install sentry && mcpizy install slack
Free to install. Connect your accounts and this workflow runs itself.