From 5d60327d92c6e609a2def0d9c6aaa33b9a8d9cb5 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Wed, 1 Oct 2025 16:07:33 -0700 Subject: [PATCH 01/11] Add Sentry MCP error monitoring cookbook MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Create comprehensive Sentry MCP cookbook following PostHog/Netlify structure - Add automated error analysis workflow with AI-powered root cause detection - Include GitHub Actions workflow for continuous error monitoring (runs every 6 hours) - Add cookbook to docs.json navigation in Cookbooks section - All links grounded in official Sentry documentation - Uses Mintlify components consistent with existing cookbooks 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- docs/docs.json | 1 + docs/guides/sentry-mcp-error-monitoring.mdx | 466 ++++++++++++++++++++ 2 files changed, 467 insertions(+) create mode 100644 docs/guides/sentry-mcp-error-monitoring.mdx diff --git a/docs/docs.json b/docs/docs.json index 94be18094b..cbf1591328 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -260,6 +260,7 @@ "icon": "book-open-cover", "pages": [ "guides/posthog-github-continuous-ai", + "guides/sentry-mcp-error-monitoring", "guides/snyk-mcp-continue-cookbook", "guides/dlt-mcp-continue-cookbook", "guides/netlify-mcp-continuous-deployment" diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx new file mode 100644 index 0000000000..dc620a0246 --- /dev/null +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -0,0 +1,466 @@ +--- +title: "Automated Error Analysis with Sentry MCP" +description: "Build an AI-powered error monitoring workflow that analyzes Sentry issues, identifies patterns, and creates actionable GitHub issues automatically." +sidebarTitle: "Sentry Error Monitoring with Continue CLI" +--- + + + An automated error monitoring system that uses Continue CLI with Sentry MCP to analyze production errors, identify root causes with AI, and create detailed GitHub issues with suggested fixes. + + +## What You'll Learn + +This cookbook teaches you to: + +- Use [Sentry MCP](https://docs.sentry.io/product/sentry-mcp/) to access [issues](https://docs.sentry.io/product/issues/), [performance data](https://docs.sentry.io/product/performance/), and [release tracking](https://docs.sentry.io/product/releases/) +- Analyze error patterns and stack traces with AI +- Leverage [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent issue analysis +- Automatically create GitHub issues with root cause analysis +- Set up continuous error monitoring with GitHub Actions + +## Prerequisites + +Before starting, ensure you have: + +- GitHub repository where you want to create issues +- [Sentry account](https://sentry.io) with an active project collecting errors +- Node.js 18+ installed locally +- [Continue CLI](https://docs.continue.dev/guides/cli) with **active credits** (required for API usage) +- [GitHub CLI](https://cli.github.com/) installed (`gh` command) + + + + ```bash + npm i -g @continuedev/cli + ``` + + + + 1. Visit [Continue Organizations](https://hub.continue.dev/settings/organizations) + 2. Sign up or log in to your Continue account + 3. Navigate to your organization settings + 4. Click **"API Keys"** and then **"+ New API Key"** + 5. Copy the API key immediately (you won't see it again!) + 6. Login to the CLI: `cn login` + + + + + Continue CLI handles complex error analysis and API interactions - you just need to provide the right prompts! + + +## Step 1: Set Up Your Credentials + +First, you'll need to gather your Sentry and GitHub API credentials. + + + + You'll need a **Sentry User Auth Token** to access issues and error data: + + 1. Go to [User Auth Tokens](https://sentry.io/settings/account/api/auth-tokens/) in Sentry + 2. Click **Create New Token** + 3. Name it "Continue CLI Error Analysis" + 4. Select these scopes: + - `org:read` - **Required** for accessing organization data + - `project:read` - **Required** for accessing projects + - `issue:read` - **Required** for reading error issues + - `issue:write` - Optional, for updating issues + - `event:read` - For detailed event data + 5. Copy the token immediately (you won't see it again!) + 6. Note your organization slug (found in your Sentry URL: `https://sentry.io/organizations/YOUR-ORG-SLUG`) + 7. Note your Sentry host URL (typically `https://sentry.io` or your self-hosted domain) + + + **Sentry MCP Connection**: The MCP server connects via OAuth to `https://mcp.sentry.dev/mcp` and handles authentication securely. For local development, you can use STDIO mode with your auth token. + + + + + GitHub CLI handles authentication automatically - no manual PAT needed: + + 1. Install GitHub CLI if not already installed + 2. Run `gh auth login` and follow the prompts + 3. Choose authentication method (browser or token) + 4. Grant necessary permissions when prompted (`issues:write` is **required** for creating issues) + + + + + + See [Sentry MCP Documentation](https://docs.sentry.io/product/sentry-mcp/) for detailed configuration options + + + The Sentry MCP supports multiple configuration methods. For Continue CLI, OAuth is recommended: + + **Option 1: OAuth Configuration (Recommended)** + + The Sentry MCP will prompt for OAuth authentication when first used. Simply follow the authorization flow. + + **Option 2: STDIO Mode with Auth Token** + + For local development, you can use STDIO mode: + ```bash + npx @sentry/mcp-server@latest --access-token=YOUR_SENTRY_TOKEN --host=sentry.io + ``` + + + + +## Sentry Error Monitoring Workflow Options + + + Choose between using the Sentry MCP directly or building custom error analysis workflows with Continue CLI. + + + + **How Sentry MCP Works**: + - Connects to your Sentry organization via OAuth + - Provides tools for accessing issues, projects, teams, and DSNs + - Integrates with [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent analysis + - Supports both hosted (`https://mcp.sentry.dev`) and self-hosted Sentry instances + + + + + **Perfect for:** Immediate error analysis with AI-powered root cause detection + + + + Add the Sentry MCP to your Continue CLI configuration. The MCP will handle OAuth authentication automatically: + + ```bash + # The Sentry MCP will prompt for OAuth on first use + cn "Show me recent Sentry errors" + ``` + + This provides: + - **Automatic authentication** via OAuth flow + - **Access to all Sentry tools**: issues, projects, teams, DSNs + - **Seer AI integration** for intelligent error analysis + + + + Navigate to your project directory and run: + ```bash + cn "Analyze recent Sentry errors and create GitHub issues for critical bugs with suggested fixes" + ``` + + That's it! Continue CLI handles everything automatically. + + + + + **Why Use Sentry MCP?** Direct integration with Sentry's API provides more reliable error data access and enables AI-powered analysis through Seer. + + + + + + + + Configure the [Sentry MCP](https://docs.sentry.io/product/sentry-mcp/) using OAuth: + + The MCP server will automatically prompt for OAuth authentication when you first use it. + + + + Test your Sentry MCP connection: + ```bash + cn "List my Sentry organizations and projects" + ``` + + + + Use this prompt template with Continue CLI to analyze Sentry errors: + + ```bash + # In cn TUI mode: + "Analyze Sentry errors from the past 24 hours: + - Group errors by root cause + - Identify the top 5 most critical issues by frequency and impact + - For each critical issue, provide: + * Stack trace analysis + * Affected user count + * First seen and last seen timestamps + * Suggested fix based on error context + - Create GitHub issues using gh CLI with: + * Title format: '🐛 [Sentry] [Error Type]: Brief description' + * Labels: 'bug', 'sentry', 'production' + * Priority labels based on severity + * Full error context and suggested fix in the body + Execute the commands and confirm each issue was created." + ``` + + + + + + + + **Why GitHub CLI over GitHub MCP**: While GitHub MCP is available, the `gh` CLI is more token-efficient, requires no API tokens (authenticated via `gh auth login`), and provides a cleaner command-line experience. + + + + To use the Sentry MCP, you need: + - **Sentry account** with at least one project + - **User Auth Token** with appropriate scopes (or OAuth flow) + - **Continue CLI** with API credits for AI analysis + + The MCP works with both Sentry's hosted service (`sentry.io`) and self-hosted instances. + + +--- + + + **Repository Labels Required**: Make sure your GitHub repository has these labels: + - `bug`, `sentry`, `production` + - `critical`, `high-priority`, `medium-priority`, `low-priority` + - `needs-investigation`, `has-fix` + + Create missing labels in your repo at: **Settings → Labels → New label** + + +## Step 2: Analyze Sentry Errors with AI + +Use Continue CLI to perform intelligent error analysis: + + + + ```bash + # In cn TUI mode: + "Show me Sentry errors from the past 7 days, grouped by error type, with frequency counts" + ``` + + + + ```bash + # In cn TUI mode: + "Find the most critical Sentry error affecting the most users in production and provide: + - Full stack trace analysis + - Affected user count and browser/OS breakdown + - Timeline of when the error started occurring + - Similar historical issues from Sentry + - Root cause hypothesis based on code context + - Suggested fix with code examples" + ``` + + + + ```bash + # In cn TUI mode: + "Analyze Sentry performance data to identify: + - Slowest transactions in the past 24 hours + - Database queries with high latency + - API endpoints with degraded performance + - Suggested optimizations for each issue" + ``` + + + + + **Available Sentry MCP Tools**: + - **Organizations**: Access org-level data and settings + - **Projects**: Query projects and their configurations + - **Issues**: Search and analyze error issues + - **Teams**: Manage team assignments + - **DSNs**: Retrieve project DSN configurations + - **Seer Integration**: Leverage [Sentry's AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent analysis + - **Release Management**: Track errors by release version + + +## Step 3: Automate GitHub Issue Creation + +Create actionable GitHub issues from Sentry errors: + +```bash +# In cn TUI mode: +"For each unresolved Sentry error with 'critical' or 'high' severity: +1. Analyze the error using Sentry MCP and Seer AI +2. Create a GitHub issue with gh CLI: + - Title: '🐛 [Sentry] [Error Type]: Brief description' + - Body with: + * Error summary and impact (affected users, frequency) + * Full stack trace + * Environment details (browser, OS, release version) + * Link to Sentry issue + * Root cause analysis from AI + * Suggested fix with code snippets + * Related Sentry issues + - Labels: 'bug', 'sentry', 'production', and severity label + - Assignees: Team member based on code ownership +3. Update Sentry issue with GitHub issue link +4. Confirm creation with GitHub issue URL" +``` + + + **Best Practice**: Link GitHub issues back to Sentry for full traceability. This creates a bidirectional connection between your error monitoring and issue tracking. + + +## Step 4: Set Up Continuous Monitoring with GitHub Actions + +Automate error monitoring to run daily and create issues for new critical errors: + +```yaml +name: Sentry Error Monitoring + +on: + schedule: + # Run every 6 hours + - cron: "0 */6 * * *" + workflow_dispatch: # Allow manual triggers + +jobs: + monitor-errors: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - uses: actions/setup-node@v4 + with: + node-version: "22" + + - name: Install Continue CLI + run: | + npm install -g @continuedev/cli + echo "✅ Continue CLI installed" + + - name: Authenticate GitHub CLI + run: | + echo "${{ secrets.GITHUB_TOKEN }}" | gh auth login --with-token + echo "✅ GitHub CLI authenticated" + + - name: Analyze Sentry Errors and Create Issues + env: + CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }} + SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }} + SENTRY_ORG: ${{ secrets.SENTRY_ORG }} + run: | + echo "🔍 Analyzing Sentry errors..." + cn -p "Using Sentry MCP, analyze errors from the past 6 hours: + 1. Filter for unresolved errors with high or critical severity + 2. Group similar errors to avoid duplicates + 3. For each unique critical error: + - Check if a GitHub issue already exists for this error + - If not, create a new issue with full analysis + - Use gh CLI: gh issue create --title 'title' --body 'body' --label 'bug,sentry,critical' + 4. Output summary with created issue URLs + + Sentry Organization: $SENTRY_ORG + Only process errors not already tracked in GitHub." + + - name: Comment on workflow run + if: always() + run: | + echo "✅ Sentry monitoring complete. Check step output for created issues." +``` + + + **Required GitHub Secrets**: + - `CONTINUE_API_KEY`: Your Continue API key from [hub.continue.dev/settings/api-keys](https://hub.continue.dev/settings/api-keys) + - `SENTRY_AUTH_TOKEN`: Your Sentry User Auth Token + - `SENTRY_ORG`: Your Sentry organization slug + - `GITHUB_TOKEN`: Automatically provided by GitHub Actions + + Add these at: **Repository Settings → Secrets and variables → Actions** + + + + **Workflow Best Practices**: + - Run every 6 hours to catch critical errors quickly + - Use duplicate detection to avoid creating multiple issues for the same error + - Filter by severity to focus on high-impact issues + - Include full error context and suggested fixes in issues + - Tag issues with appropriate labels for team routing + + +## What You've Built + +After completing this guide, you have a complete **Sentry-powered error monitoring system** that: + +- **Monitors production errors** - Automatically fetches and analyzes Sentry issues every 6 hours + +- **Identifies critical bugs** - Uses AI and Sentry's Seer to spot high-impact errors + +- **Creates actionable tasks** - Generates GitHub issues with root cause analysis and suggested fixes + +- **Runs autonomously** - Operates continuously without manual intervention using GitHub Actions + +- **Scales with your app** - Handles growing error volumes and complexity automatically + + + Your system now operates at **[Level 2 Continuous AI](https://blog.continue.dev/what-is-continuous-ai-a-developers-guide/)** - AI handles routine error analysis with human oversight through GitHub issue review and resolution. + + +## Advanced Error Analysis Prompts + +Enhance your workflow with these advanced Continue CLI prompts: + + + + "Compare error rates before and after the latest [Sentry release](https://docs.sentry.io/product/releases/) to identify regressions introduced in the deployment" + + + "Analyze Sentry error trends over the past 30 days and identify emerging issues before they become critical" + + + "Identify which errors are affecting the most unique users and prioritize fixes based on user impact" + + + "Cross-reference Sentry [performance issues](https://docs.sentry.io/product/performance/) with error spikes to identify root causes" + + + +## Security Best Practices + + + **Protect Your API Keys**: + - Store all credentials as GitHub Secrets, never in code + - Use Continue CLI's secure secret storage + - Limit Sentry token scopes to minimum required permissions + - Rotate API keys regularly (every 90 days recommended) + - Monitor token usage for unusual activity + - Use OAuth when possible for better security + + +## Troubleshooting + +### Sentry MCP Connection Issues + +If you encounter connection issues: + +1. Verify OAuth authentication is complete +2. Check your Sentry organization access +3. Ensure the MCP server URL is correct (`https://mcp.sentry.dev/mcp`) +4. For self-hosted Sentry, verify your host URL is configured correctly + +See the [Sentry MCP GitHub Issues](https://github.com/getsentry/sentry-mcp/issues) for known issues and solutions. + +### Common Error Analysis Issues + +| Issue | Solution | +|-------|----------| +| No errors returned | Verify your Sentry project has collected errors recently | +| OAuth prompt not appearing | Check that Continue CLI has proper MCP configuration | +| Duplicate GitHub issues | Implement duplicate detection in your prompts | +| Missing error context | Ensure your Sentry token has `event:read` scope | + +## Next Steps + +- Explore [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for enhanced error analysis +- Set up [Sentry performance monitoring](https://docs.sentry.io/product/performance/) +- Configure [Sentry release tracking](https://docs.sentry.io/product/releases/) for deployment correlation +- Integrate [Slack MCP](https://hub.continue.dev/slack/slack-mcp) for error alerts +- Join the [Continue Discord](https://discord.gg/continue) for support + +## Resources + +- [Sentry MCP Documentation](https://docs.sentry.io/product/sentry-mcp/) +- [Sentry API Documentation](https://docs.sentry.io/api/) +- [Sentry Issues Guide](https://docs.sentry.io/product/issues/) +- [Sentry Performance Monitoring](https://docs.sentry.io/product/performance/) +- [Sentry Release Tracking](https://docs.sentry.io/product/releases/) +- [Sentry Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) +- [Sentry MCP GitHub Repository](https://github.com/getsentry/sentry-mcp) +- [GitHub CLI Documentation](https://cli.github.com/) +- [Continue CLI Guide](https://docs.continue.dev/guides/cli) +- [Continuous AI Best Practices](https://blog.continue.dev/what-is-continuous-ai-a-developers-guide/) From 2429757ee0b7bc59a2d24702eb0b6abd980bd758 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 15:25:03 -0700 Subject: [PATCH 02/11] Address Patrick's feedback on Sentry MCP cookbook - Make sidebar title match page title - Focus on Sentry Issues only (remove references to Releases/Performance in learning section) - Remove all references to Sentry's Seer AI to avoid confusion - Simplify MCP configuration approach - Fix comment formatting in code blocks for better copy/paste - Consider PR creation instead of just issues (keeping issues for now as PRs need more context) Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 24 ++++++++++----------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index dc620a0246..751871a664 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -1,7 +1,7 @@ --- title: "Automated Error Analysis with Sentry MCP" description: "Build an AI-powered error monitoring workflow that analyzes Sentry issues, identifies patterns, and creates actionable GitHub issues automatically." -sidebarTitle: "Sentry Error Monitoring with Continue CLI" +sidebarTitle: "Automated Error Analysis with Sentry MCP" --- @@ -12,9 +12,9 @@ sidebarTitle: "Sentry Error Monitoring with Continue CLI" This cookbook teaches you to: -- Use [Sentry MCP](https://docs.sentry.io/product/sentry-mcp/) to access [issues](https://docs.sentry.io/product/issues/), [performance data](https://docs.sentry.io/product/performance/), and [release tracking](https://docs.sentry.io/product/releases/) +- Use [Sentry MCP](https://docs.sentry.io/product/sentry-mcp/) to access [issues](https://docs.sentry.io/product/issues/) - Analyze error patterns and stack traces with AI -- Leverage [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent issue analysis + - Automatically create GitHub issues with root cause analysis - Set up continuous error monitoring with GitHub Actions @@ -116,7 +116,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. **How Sentry MCP Works**: - Connects to your Sentry organization via OAuth - Provides tools for accessing issues, projects, teams, and DSNs - - Integrates with [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent analysis + - Supports both hosted (`https://mcp.sentry.dev`) and self-hosted Sentry instances @@ -136,7 +136,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. This provides: - **Automatic authentication** via OAuth flow - **Access to all Sentry tools**: issues, projects, teams, DSNs - - **Seer AI integration** for intelligent error analysis + @@ -150,7 +150,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. - **Why Use Sentry MCP?** Direct integration with Sentry's API provides more reliable error data access and enables AI-powered analysis through Seer. + **Why Use Sentry MCP?** Direct integration with Sentry's API provides more reliable error data access and enables AI-powered analysis. @@ -174,7 +174,6 @@ First, you'll need to gather your Sentry and GitHub API credentials. Use this prompt template with Continue CLI to analyze Sentry errors: ```bash - # In cn TUI mode: "Analyze Sentry errors from the past 24 hours: - Group errors by root cause - Identify the top 5 most critical issues by frequency and impact @@ -264,8 +263,7 @@ Use Continue CLI to perform intelligent error analysis: - **Issues**: Search and analyze error issues - **Teams**: Manage team assignments - **DSNs**: Retrieve project DSN configurations - - **Seer Integration**: Leverage [Sentry's AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for intelligent analysis - - **Release Management**: Track errors by release version + ## Step 3: Automate GitHub Issue Creation @@ -275,7 +273,7 @@ Create actionable GitHub issues from Sentry errors: ```bash # In cn TUI mode: "For each unresolved Sentry error with 'critical' or 'high' severity: -1. Analyze the error using Sentry MCP and Seer AI +1. Analyze the error using Sentry MCP 2. Create a GitHub issue with gh CLI: - Title: '🐛 [Sentry] [Error Type]: Brief description' - Body with: @@ -379,7 +377,7 @@ After completing this guide, you have a complete **Sentry-powered error monitori - **Monitors production errors** - Automatically fetches and analyzes Sentry issues every 6 hours -- **Identifies critical bugs** - Uses AI and Sentry's Seer to spot high-impact errors +- **Identifies critical bugs** - Uses AI to spot high-impact errors - **Creates actionable tasks** - Generates GitHub issues with root cause analysis and suggested fixes @@ -446,7 +444,7 @@ See the [Sentry MCP GitHub Issues](https://github.com/getsentry/sentry-mcp/issue ## Next Steps -- Explore [Sentry's Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) for enhanced error analysis + - Set up [Sentry performance monitoring](https://docs.sentry.io/product/performance/) - Configure [Sentry release tracking](https://docs.sentry.io/product/releases/) for deployment correlation - Integrate [Slack MCP](https://hub.continue.dev/slack/slack-mcp) for error alerts @@ -459,7 +457,7 @@ See the [Sentry MCP GitHub Issues](https://github.com/getsentry/sentry-mcp/issue - [Sentry Issues Guide](https://docs.sentry.io/product/issues/) - [Sentry Performance Monitoring](https://docs.sentry.io/product/performance/) - [Sentry Release Tracking](https://docs.sentry.io/product/releases/) -- [Sentry Seer AI](https://docs.sentry.io/product/ai-in-sentry/seer/) + - [Sentry MCP GitHub Repository](https://github.com/getsentry/sentry-mcp) - [GitHub CLI Documentation](https://cli.github.com/) - [Continue CLI Guide](https://docs.continue.dev/guides/cli) From 3f2d3907ee93dac18b92698d05397d893513e41d Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 15:37:28 -0700 Subject: [PATCH 03/11] Add Sentry and dlt cookbooks to guides overview - Add Sentry MCP error monitoring cookbook to the MCP Integration section - Add dlt data pipelines cookbook to the MCP Integration section - Maintain alphabetical ordering within the MCP cookbook list Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/overview.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/guides/overview.mdx b/docs/guides/overview.mdx index 3ca80dae01..f27572a635 100644 --- a/docs/guides/overview.mdx +++ b/docs/guides/overview.mdx @@ -19,8 +19,10 @@ description: "Comprehensive collection of practical guides for Continue includin Step-by-step guides for integrating Model Context Protocol (MCP) servers with Continue: +- [Sentry Error Monitoring Cookbook](/guides/sentry-mcp-error-monitoring) - Automated error analysis with Sentry MCP to identify patterns and create actionable GitHub issues - [PostHog Session Analysis Cookbook](/guides/posthog-github-continuous-ai) - Analyze user behavior data to optimize your codebase with automatic issue creation - [Netlify Performance Optimization Cookbook](/guides/netlify-mcp-continuous-deployment) - Optimize web performance with A/B testing and automated monitoring using Netlify MCP +- [dlt Data Pipelines Cookbook](/guides/dlt-mcp-continue-cookbook) - Build and debug data pipelines with dlt MCP using natural language commands - [Snyk + Continue Hub Agent Cookbook (MCP)](/guides/snyk-mcp-continue-cookbook) - Integrate Snyk MCP via Continue Hub to scan code, deps, IaC, and containers ## What Advanced Tutorials Are Available From fb7125458f4e28169eafc6a46fe3552b86b676a4 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:11:53 -0700 Subject: [PATCH 04/11] Add Quick Start section to Sentry guide with pre-built agent - Added Quick Start section similar to PostHog guide - Featured continuedev/sentry-continuous-ai agent from Continue Hub - Improved messaging and structure for faster onboarding - Updated Agent Requirements accordion with Pro Plan option - Fixed table formatting with left-aligned columns - Aligned GitHub CLI vs MCP messaging with PostHog guide Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 123 +++++++++++--------- 1 file changed, 67 insertions(+), 56 deletions(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 751871a664..53037a49b2 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -58,14 +58,17 @@ First, you'll need to gather your Sentry and GitHub API credentials. You'll need a **Sentry User Auth Token** to access issues and error data: 1. Go to [User Auth Tokens](https://sentry.io/settings/account/api/auth-tokens/) in Sentry + - For self-hosted Sentry, use: `https://YOUR-SENTRY-DOMAIN/settings/account/api/auth-tokens/` 2. Click **Create New Token** 3. Name it "Continue CLI Error Analysis" - 4. Select these scopes: - - `org:read` - **Required** for accessing organization data - - `project:read` - **Required** for accessing projects - - `issue:read` - **Required** for reading error issues - - `issue:write` - Optional, for updating issues - - `event:read` - For detailed event data + 4. **Select these permission scopes** (required for full functionality): + - `org:read` - **Required** - Access organization information + - `project:read` - **Required** - Read project configurations + - `project:releases` - **Required** - Access release information for deployment tracking + - `event:read` - **Required** - Read detailed error event data and stack traces + - `event:write` - Optional - Update error events (for marking as resolved) + - `member:read` - Recommended - Read team member information for auto-assignment + - `team:read` - Recommended - Access team data for routing issues 5. Copy the token immediately (you won't see it again!) 6. Note your organization slug (found in your Sentry URL: `https://sentry.io/organizations/YOUR-ORG-SLUG`) 7. Note your Sentry host URL (typically `https://sentry.io` or your self-hosted domain) @@ -109,48 +112,50 @@ First, you'll need to gather your Sentry and GitHub API credentials. ## Sentry Error Monitoring Workflow Options - Choose between using the Sentry MCP directly or building custom error analysis workflows with Continue CLI. + Skip the manual setup and use our pre-built Sentry Continuous AI agent that includes + optimized prompts, rules, and the Sentry MCP for more consistent results. **How Sentry MCP Works**: - Connects to your Sentry organization via OAuth - Provides tools for accessing issues, projects, teams, and DSNs - - Supports both hosted (`https://mcp.sentry.dev`) and self-hosted Sentry instances + - Automatically handles authentication and API interactions - **Perfect for:** Immediate error analysis with AI-powered root cause detection + **Perfect for:** Immediate error analysis with AI-powered root cause detection and built-in debugging - - Add the Sentry MCP to your Continue CLI configuration. The MCP will handle OAuth authentication automatically: - + + Visit the [Sentry Continuous AI Agent](https://hub.continue.dev/continuedev/sentry-continuous-ai) on Continue Hub and click **"Install Agent"** or run: + ```bash - # The Sentry MCP will prompt for OAuth on first use - cn "Show me recent Sentry errors" + cn --config continuedev/sentry-continuous-ai ``` - This provides: + This agent includes: + - **Optimized prompts** for Sentry error analysis and GitHub issue creation + - **Built-in rules** for consistent formatting and error handling + - **[Sentry MCP](https://docs.sentry.io/product/sentry-mcp/)** for more reliable API interactions - **Automatic authentication** via OAuth flow - - **Access to all Sentry tools**: issues, projects, teams, DSNs - - Navigate to your project directory and run: - ```bash - cn "Analyze recent Sentry errors and create GitHub issues for critical bugs with suggested fixes" + Navigate to your project directory and enter this prompt in the Continue CLI TUI: + + ``` + Analyze recent Sentry errors and create GitHub issues for critical bugs with suggested fixes ``` - That's it! Continue CLI handles everything automatically. + That's it! The agent handles everything automatically. - **Why Use Sentry MCP?** Direct integration with Sentry's API provides more reliable error data access and enables AI-powered analysis. + **Why Use the Agent?** Results are more consistent and debugging is easier thanks to the Sentry MCP integration and pre-tested prompts. @@ -164,17 +169,18 @@ First, you'll need to gather your Sentry and GitHub API credentials. - Test your Sentry MCP connection: - ```bash - cn "List my Sentry organizations and projects" + Test your Sentry MCP connection with this prompt: + + ``` + List my Sentry organizations and projects ``` Use this prompt template with Continue CLI to analyze Sentry errors: - ```bash - "Analyze Sentry errors from the past 24 hours: + ``` + Analyze Sentry errors from the past 24 hours: - Group errors by root cause - Identify the top 5 most critical issues by frequency and impact - For each critical issue, provide: @@ -187,7 +193,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. * Labels: 'bug', 'sentry', 'production' * Priority labels based on severity * Full error context and suggested fix in the body - Execute the commands and confirm each issue was created." + Execute the commands and confirm each issue was created. ``` @@ -196,16 +202,21 @@ First, you'll need to gather your Sentry and GitHub API credentials. - **Why GitHub CLI over GitHub MCP**: While GitHub MCP is available, the `gh` CLI is more token-efficient, requires no API tokens (authenticated via `gh auth login`), and provides a cleaner command-line experience. + **Why GitHub CLI over GitHub MCP**: While GitHub MCP is available, it can be + token-expensive to run. The `gh` CLI is more efficient, requires no API tokens + (authenticated via `gh auth login`), and provides a cleaner command-line + experience. GitHub MCP remains an option if you prefer full MCP integration. - - To use the Sentry MCP, you need: + + To use the pre-built agent, you need either: + - **Continue CLI Pro Plan** with the models add-on, OR + - **Your own API keys** added to Continue Hub secrets (same as Step 1) + + The agent will automatically detect and use your configuration. For Sentry MCP: - **Sentry account** with at least one project - **User Auth Token** with appropriate scopes (or OAuth flow) - - **Continue CLI** with API credits for AI analysis - - The MCP works with both Sentry's hosted service (`sentry.io`) and self-hosted instances. + - The MCP works with both Sentry's hosted service (`sentry.io`) and self-hosted instances --- @@ -221,37 +232,37 @@ First, you'll need to gather your Sentry and GitHub API credentials. ## Step 2: Analyze Sentry Errors with AI -Use Continue CLI to perform intelligent error analysis: +Use Continue CLI to perform intelligent error analysis. Enter these prompts in the Continue CLI TUI: - ```bash - # In cn TUI mode: - "Show me Sentry errors from the past 7 days, grouped by error type, with frequency counts" + **Prompt:** + ``` + Show me Sentry errors from the past 7 days, grouped by error type, with frequency counts ``` - ```bash - # In cn TUI mode: - "Find the most critical Sentry error affecting the most users in production and provide: + **Prompt:** + ``` + Find the most critical Sentry error affecting the most users in production and provide: - Full stack trace analysis - Affected user count and browser/OS breakdown - Timeline of when the error started occurring - Similar historical issues from Sentry - Root cause hypothesis based on code context - - Suggested fix with code examples" + - Suggested fix with code examples ``` - ```bash - # In cn TUI mode: - "Analyze Sentry performance data to identify: + **Prompt:** + ``` + Analyze Sentry performance data to identify: - Slowest transactions in the past 24 hours - Database queries with high latency - API endpoints with degraded performance - - Suggested optimizations for each issue" + - Suggested optimizations for each issue ``` @@ -268,11 +279,11 @@ Use Continue CLI to perform intelligent error analysis: ## Step 3: Automate GitHub Issue Creation -Create actionable GitHub issues from Sentry errors: +Create actionable GitHub issues from Sentry errors. Enter this prompt in the Continue CLI TUI: -```bash -# In cn TUI mode: -"For each unresolved Sentry error with 'critical' or 'high' severity: +**Prompt:** +``` +For each unresolved Sentry error with 'critical' or 'high' severity: 1. Analyze the error using Sentry MCP 2. Create a GitHub issue with gh CLI: - Title: '🐛 [Sentry] [Error Type]: Brief description' @@ -287,7 +298,7 @@ Create actionable GitHub issues from Sentry errors: - Labels: 'bug', 'sentry', 'production', and severity label - Assignees: Team member based on code ownership 3. Update Sentry issue with GitHub issue link -4. Confirm creation with GitHub issue URL" +4. Confirm creation with GitHub issue URL ``` @@ -395,16 +406,16 @@ Enhance your workflow with these advanced Continue CLI prompts: - "Compare error rates before and after the latest [Sentry release](https://docs.sentry.io/product/releases/) to identify regressions introduced in the deployment" + Compare error rates before and after the latest [Sentry release](https://docs.sentry.io/product/releases/) to identify regressions introduced in the deployment - "Analyze Sentry error trends over the past 30 days and identify emerging issues before they become critical" + Analyze Sentry error trends over the past 30 days and identify emerging issues before they become critical - "Identify which errors are affecting the most unique users and prioritize fixes based on user impact" + Identify which errors are affecting the most unique users and prioritize fixes based on user impact - "Cross-reference Sentry [performance issues](https://docs.sentry.io/product/performance/) with error spikes to identify root causes" + Cross-reference Sentry [performance issues](https://docs.sentry.io/product/performance/) with error spikes to identify root causes @@ -436,7 +447,7 @@ See the [Sentry MCP GitHub Issues](https://github.com/getsentry/sentry-mcp/issue ### Common Error Analysis Issues | Issue | Solution | -|-------|----------| +|:------|:---------| | No errors returned | Verify your Sentry project has collected errors recently | | OAuth prompt not appearing | Check that Continue CLI has proper MCP configuration | | Duplicate GitHub issues | Implement duplicate detection in your prompts | From a47cf523f9398955348d2122d2590a89314dc784 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:13:56 -0700 Subject: [PATCH 05/11] Move Configure Sentry MCP tab to first position - Reordered tabs in Step 1 to prioritize MCP configuration - Configure Sentry MCP is now the leftmost tab for better visibility Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 40 ++++++++++----------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 53037a49b2..14f0800226 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -54,6 +54,26 @@ Before starting, ensure you have: First, you'll need to gather your Sentry and GitHub API credentials. + + + + See [Sentry MCP Documentation](https://docs.sentry.io/product/sentry-mcp/) for detailed configuration options + + + The Sentry MCP supports multiple configuration methods. For Continue CLI, OAuth is recommended: + + **Option 1: OAuth Configuration (Recommended)** + + The Sentry MCP will prompt for OAuth authentication when first used. Simply follow the authorization flow. + + **Option 2: STDIO Mode with Auth Token** + + For local development, you can use STDIO mode: + ```bash + npx @sentry/mcp-server@latest --access-token=YOUR_SENTRY_TOKEN --host=sentry.io + ``` + + You'll need a **Sentry User Auth Token** to access issues and error data: @@ -87,26 +107,6 @@ First, you'll need to gather your Sentry and GitHub API credentials. 4. Grant necessary permissions when prompted (`issues:write` is **required** for creating issues) - - - - See [Sentry MCP Documentation](https://docs.sentry.io/product/sentry-mcp/) for detailed configuration options - - - The Sentry MCP supports multiple configuration methods. For Continue CLI, OAuth is recommended: - - **Option 1: OAuth Configuration (Recommended)** - - The Sentry MCP will prompt for OAuth authentication when first used. Simply follow the authorization flow. - - **Option 2: STDIO Mode with Auth Token** - - For local development, you can use STDIO mode: - ```bash - npx @sentry/mcp-server@latest --access-token=YOUR_SENTRY_TOKEN --host=sentry.io - ``` - - ## Sentry Error Monitoring Workflow Options From 121ed02a798c83856940978aecf62cfa5e6c62a0 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:15:45 -0700 Subject: [PATCH 06/11] Update STDIO mode example with host parameter and environment variables - Added clarification that STDIO mode is for local development or self-hosted Sentry - Included environment variable configuration option (SENTRY_ACCESS_TOKEN, SENTRY_HOST) - Added Info box explaining --host parameter requirement with examples - Matches official Sentry MCP documentation Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 14f0800226..81128d5454 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -68,11 +68,20 @@ First, you'll need to gather your Sentry and GitHub API credentials. **Option 2: STDIO Mode with Auth Token** - For local development, you can use STDIO mode: + For local development or self-hosted Sentry installations, you can use STDIO mode: ```bash npx @sentry/mcp-server@latest --access-token=YOUR_SENTRY_TOKEN --host=sentry.io ``` + Or use environment variables: + ```bash + SENTRY_ACCESS_TOKEN=your-token SENTRY_HOST=sentry.io + ``` + + + The `--host` parameter is required and should point to your Sentry instance (e.g., `sentry.io` or `sentry.example.com` for self-hosted). + + You'll need a **Sentry User Auth Token** to access issues and error data: From 63385e25ae1d46ef08c7b064d90436b0c7034899 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:19:29 -0700 Subject: [PATCH 07/11] Add rocket emoji back to Card title - SVG icon not rendering properly, using emoji fallback - Matches PostHog guide formatting Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 81128d5454..df99c413b2 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -117,7 +117,6 @@ First, you'll need to gather your Sentry and GitHub API credentials. - ## Sentry Error Monitoring Workflow Options From 02ac1bae7950d6fc6f09d19650dcf76c83d4c8b7 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:21:45 -0700 Subject: [PATCH 08/11] Remove rocket emoji from Card title - Let rocket icon handle the visual representation - Cleaner appearance without duplicate visual elements Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index df99c413b2..1ac1c30a15 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -119,7 +119,7 @@ First, you'll need to gather your Sentry and GitHub API credentials. ## Sentry Error Monitoring Workflow Options - + Skip the manual setup and use our pre-built Sentry Continuous AI agent that includes optimized prompts, rules, and the Sentry MCP for more consistent results. From e135cae7eb92140e122bb2d620f050d2fc7699f7 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:25:19 -0700 Subject: [PATCH 09/11] Add Sentry GitHub Action integration with Continue CLI - Integrated Sentry Release GitHub Action for release tracking - Enhanced workflow to create Sentry releases on push to main - Updated Continue CLI prompt to generate comprehensive AI-powered issue descriptions - Added SENTRY_PROJECT to required secrets - Improved workflow summary with GitHub Step Summary - Added documentation on combining Sentry releases with Continue CLI - Link to official Sentry GitHub Actions documentation Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 67 ++++++++++++++++++--- 1 file changed, 59 insertions(+), 8 deletions(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 1ac1c30a15..db2598cb30 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -315,12 +315,23 @@ For each unresolved Sentry error with 'critical' or 'high' severity: ## Step 4: Set Up Continuous Monitoring with GitHub Actions -Automate error monitoring to run daily and create issues for new critical errors: +Automate error monitoring with the [Sentry Release GitHub Action](https://docs.sentry.io/product/releases/setup/release-automation/github-actions/) and Continue CLI to create comprehensive, AI-powered issue descriptions: + + + **Why Combine Sentry Releases with Continue CLI?** + - **Release Tracking**: Associate errors with specific deployments + - **AI-Powered Analysis**: Continue CLI generates detailed issue descriptions with root cause analysis + - **Better Context**: Link errors to commits and pull requests + - **Automated Workflows**: Create issues with full stack traces and suggested fixes + ```yaml name: Sentry Error Monitoring on: + push: + branches: + - main schedule: # Run every 6 hours - cron: "0 */6 * * *" @@ -331,11 +342,23 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 + with: + fetch-depth: 0 - uses: actions/setup-node@v4 with: node-version: "22" + # Create Sentry release for better error tracking + - name: Create Sentry release + uses: getsentry/action-release@v1 + env: + SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }} + SENTRY_ORG: ${{ secrets.SENTRY_ORG }} + SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }} + with: + environment: production + - name: Install Continue CLI run: | npm install -g @continuedev/cli @@ -351,31 +374,56 @@ jobs: CONTINUE_API_KEY: ${{ secrets.CONTINUE_API_KEY }} SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }} SENTRY_ORG: ${{ secrets.SENTRY_ORG }} + SENTRY_PROJECT: ${{ secrets.SENTRY_PROJECT }} run: | echo "🔍 Analyzing Sentry errors..." - cn -p "Using Sentry MCP, analyze errors from the past 6 hours: + + # Use Continue CLI to analyze errors and generate comprehensive issue descriptions + cn -p "Using Sentry MCP, analyze errors from the past 6 hours for project $SENTRY_PROJECT: 1. Filter for unresolved errors with high or critical severity 2. Group similar errors to avoid duplicates 3. For each unique critical error: + - Generate a comprehensive issue description including: + * Error summary with frequency and user impact metrics + * Full stack trace with highlighted problem areas + * Environment details (browser, OS, release version) + * Link to Sentry issue dashboard + * Root cause analysis using AI + * Step-by-step reproduction if available + * Suggested fix with code examples + * Related errors or patterns - Check if a GitHub issue already exists for this error - - If not, create a new issue with full analysis - - Use gh CLI: gh issue create --title 'title' --body 'body' --label 'bug,sentry,critical' - 4. Output summary with created issue URLs + - If not, create a new issue with the generated description + - Use gh CLI: gh issue create --title '[Sentry] [Error Type]: Brief description' --body 'AI-generated comprehensive analysis' --label 'bug,sentry,critical,needs-investigation' + - Link the GitHub issue back to Sentry + 4. Generate a summary report with: + - Total errors analyzed + - New issues created with URLs + - Errors skipped (already tracked) + - Release correlation if available Sentry Organization: $SENTRY_ORG + Project: $SENTRY_PROJECT Only process errors not already tracked in GitHub." - - name: Comment on workflow run + - name: Post workflow summary if: always() run: | - echo "✅ Sentry monitoring complete. Check step output for created issues." + echo "## 📊 Sentry Error Monitoring Summary" >> $GITHUB_STEP_SUMMARY + echo "✅ Workflow completed at $(date)" >> $GITHUB_STEP_SUMMARY + echo "" >> $GITHUB_STEP_SUMMARY + echo "Check the 'Analyze Sentry Errors' step above for:" >> $GITHUB_STEP_SUMMARY + echo "- Number of errors analyzed" >> $GITHUB_STEP_SUMMARY + echo "- GitHub issues created" >> $GITHUB_STEP_SUMMARY + echo "- Errors already tracked" >> $GITHUB_STEP_SUMMARY ``` **Required GitHub Secrets**: - `CONTINUE_API_KEY`: Your Continue API key from [hub.continue.dev/settings/api-keys](https://hub.continue.dev/settings/api-keys) - - `SENTRY_AUTH_TOKEN`: Your Sentry User Auth Token + - `SENTRY_AUTH_TOKEN`: Your Sentry User Auth Token (needs scopes: `org:read`, `project:read`, `event:read`) - `SENTRY_ORG`: Your Sentry organization slug + - `SENTRY_PROJECT`: Your Sentry project slug - `GITHUB_TOKEN`: Automatically provided by GitHub Actions Add these at: **Repository Settings → Secrets and variables → Actions** @@ -384,10 +432,13 @@ jobs: **Workflow Best Practices**: - Run every 6 hours to catch critical errors quickly + - Create Sentry releases on push to track error-to-deployment correlation + - Use Continue CLI to generate comprehensive, AI-powered issue descriptions - Use duplicate detection to avoid creating multiple issues for the same error - Filter by severity to focus on high-impact issues - Include full error context and suggested fixes in issues - Tag issues with appropriate labels for team routing + - Link GitHub issues back to Sentry for bidirectional tracking ## What You've Built From 14b356a8d3a1be65ae2014a2a17e08b9586368d4 Mon Sep 17 00:00:00 2001 From: Brian 'bdougie' Douglas Date: Thu, 2 Oct 2025 16:29:26 -0700 Subject: [PATCH 10/11] Update sidebar title to start with 'Sentry' - Changed sidebarTitle from 'Automated Error Analysis with Sentry MCP' to 'Sentry Automated Error Analysis with MCP' - Improves discoverability by having Sentry as the first word Generated with [Continue](https://continue.dev) Co-Authored-By: Continue --- docs/guides/sentry-mcp-error-monitoring.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index db2598cb30..31384919cc 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -1,7 +1,7 @@ --- title: "Automated Error Analysis with Sentry MCP" description: "Build an AI-powered error monitoring workflow that analyzes Sentry issues, identifies patterns, and creates actionable GitHub issues automatically." -sidebarTitle: "Automated Error Analysis with Sentry MCP" +sidebarTitle: "Sentry Automated Error Analysis with MCP" --- From 1d3ea01d03c5619abdc4470a2a2b7d5cfad67740 Mon Sep 17 00:00:00 2001 From: Brian Douglas Date: Thu, 2 Oct 2025 16:42:11 -0700 Subject: [PATCH 11/11] Update sentry-mcp-error-monitoring.mdx Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> --- docs/guides/sentry-mcp-error-monitoring.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/sentry-mcp-error-monitoring.mdx b/docs/guides/sentry-mcp-error-monitoring.mdx index 31384919cc..bcbe81f9c3 100644 --- a/docs/guides/sentry-mcp-error-monitoring.mdx +++ b/docs/guides/sentry-mcp-error-monitoring.mdx @@ -421,7 +421,7 @@ jobs: **Required GitHub Secrets**: - `CONTINUE_API_KEY`: Your Continue API key from [hub.continue.dev/settings/api-keys](https://hub.continue.dev/settings/api-keys) - - `SENTRY_AUTH_TOKEN`: Your Sentry User Auth Token (needs scopes: `org:read`, `project:read`, `event:read`) + - `SENTRY_AUTH_TOKEN`: Your Sentry User Auth Token (needs scopes: `org:read`, `project:read`, `project:releases`, `event:read`) - `SENTRY_ORG`: Your Sentry organization slug - `SENTRY_PROJECT`: Your Sentry project slug - `GITHUB_TOKEN`: Automatically provided by GitHub Actions