📋 Copy Blueprint Command { } Inspect JSON API Ground-Truth Source ↗

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor

### 1. The Workflow Bottleneck & Problem Statement A single broken release can flood Slack with 500 identical error alerts while nobody knows which PR introduced the regression. ### 2. Synthesized Agent Architecture & Connected Stack **Production Sentry Spike to Deduplicated Linear Issue & Root-Cause Brief** (`sentry-to-linear-incident-triage`) is a verified production blueprint curated from **@getsentry**'s real-world implementation. - **Primary Capability:** Detects new high-frequency Sentry exceptions, resolves the offending commit via `git blame`, and creates a single deduplicated Linear ticket with fix hints. - **Connected Tool Stack:** Sentry Official MCP, GitHub MCP, Linear Official MCP, Slack - **Execution Governance:** `Read-Only Discovery` → `Deterministic Policy Check` → `Ask-First Human Approval` - **Certified Builder Source:** [@getsentry](https://github.com/getsentry/sentry-mcp) ### 3. Step-by-Step Implementation Blueprint 1. **Trigger & Data Ingestion:** Configure your agent routine to watch **Sentry Official MCP** on a scheduled cadence or event webhook. Treat all external text as untrusted data inside XML fences. 2. **Cross-System Enrichment & Verification:** Query **GitHub MCP** to validate live capacity, account status, or code state before generating recommendations. 3. **Human-in-the-Loop Action Staging:** Post a structured summary card to **Slack** with 1-click approve/edit controls so your team retains full oversight. ### 4. Copy-Paste System Prompt & Routine Configuration ```text Implement the 'Production Sentry Spike to Deduplicated Linear Issue & Root-Cause Brief' workflow curated with @getsentry. 1. OBJECTIVE: Detects new high-frequency Sentry exceptions, resolves the offending commit via `git blame`, and creates a single deduplicated Linear ticket with fix hints. 2. CONNECTED TOOL STACK: Sentry Official MCP, GitHub MCP, Linear Official MCP, Slack 3. STEP-BY-STEP EXECUTION LOOP: - Step A (Ingest & Ground): Query live inputs from Sentry Official MCP and cross-reference state in GitHub MCP. - Step B (Analyze & Validate): Apply strict filtering rules, verify schema/policy constraints, and flag any anomalies or missing fields. - Step C (Stage & Report): Prepare the structured output, draft replies/tickets in Slack, and request human confirmation before executing any external send or production write. ``` ### 5. Measured ROI & Production Impact - **Verified Outcome:** Reduces Mean Time to Resolution (MTTR) by 60% by linking every error spike directly to the introducing PR. - **Builder Portfolio:** [Explore all capabilities by @getsentry →](/u/getsentry)

Tags: #sentry-to-linear-incident-triage#use-case#engineering#getsentry#sentry-official-mcp#github-mcp

View All 7 Items by @getsentry →

mcp · ⚡ 83

Sentry Official MCP — Stack-Trace Root-Cause & Seer Issue Triage

Official Sentry MCP server: inspect production exceptions, resolve source-mapped stack traces, query release regression metrics, and invoke Seer root-cause

mcp · ⚡ 93

PagerDuty On-Call Schedules, Incident Escalation & Runbook MCP

Check current on-call engineer rotations, inspect active PagerDuty incidents and alerts, attach diagnostic notes, and acknowledge pages safely.

mcp · ⚡ 79

Datadog APM Traces, Log Explorer & Active Monitor Alerts MCP

Query Datadog APM latency percentiles, search structured production logs, inspect triggered P1/P2 monitor alerts, and correlate incident timelines.