Sentry MCP: fix Sentry error in Empower website

Note

This tutorial is based solely on the provided transcript. It teaches how to use the Sentry MCP Server within Warp to fetch live error data from Sentry, analyze stack traces, and automatically generate fixes for issues in your codebase.

Overview

The Sentry MCP server gives Warp’s agents access to authenticated Sentry error data.
This enables detailed diagnostics and automated fixes that would otherwise be impossible using AI alone.

You’ll learn how to:

• Connect the Sentry MCP server inside Warp.
• Trigger live error retrieval from Sentry.
• Diagnose code issues and generate patches automatically.
• Integrate Sentry debugging into your daily development loop.

1. Set up the Sentry MCP server

   Open the MCP panel in Warp:

   • macOS: Cmd+Shift+P
   • Windows/Linux: Ctrl+Shift+P
     Search for “MCP” and select the MCP Panel.

   Click Add, then paste your configuration:

   {
     "sentry": {
       "command": "npx",
       "args": [
         "-y",
         "mcp-remote@latest",
         "https://mcp.sentry.dev/mcp"
       ],
       "env": {},
       "working_directory": null
     }
   }

   Save the configuration and ensure it appears in the MCP panel.

2. Run your app and trigger an error

   We’re using the Empower Plant repository — Sentry’s official demo project. This fake e-commerce app includes a React frontend and multiple backends, each containing intentional bugs for testing.

   Run the app locally:

   npm install
   npm start

   Open the site in your browser and trigger a few known errors.

3. Capture the error in Sentry

   1. Go to your Sentry Dashboard.
   2. Locate the triggered issue (for example, a TypeError).
   3. Copy the issue’s URL from the Sentry interface.

   Example:

   https://sentry.io/organizations/demo/issues/12345/

4. Diagnose the error using Warp

   Back in Warp, prompt the agent to fetch and analyze the issue:

   Diagnose this Sentry error and show where it’s coming from in my code.
   Create a fix.

   The Sentry MCP calls getIssueDetails, fetching the stack trace and error metadata directly from Sentry. Warp then scans your local codebase, cross-references the error location, and identifies the root cause.

   From this example:

   The issue was caused by calling .toUpperCase() on an array instead of a string.

   Warp’s agent automatically writes a fix — changing the code to handle the array properly.

5. Apply the generated fix

   Warp produces a suggested code change inline. Review the diff and apply it automatically with one click.

6. Integrate into your workflow

   Use Sentry MCP whenever you encounter production or staging errors. Warp can pull the latest issues, analyze them, and suggest patches.

   Ideal for:

   • Debugging live production errors.
   • Triaging complex stack traces.
   • Creating immediate hot-fixes without switching tools.

   Tip

   With Sentry MCP, Warp becomes a live debugging console — connecting your code editor, terminal, and Sentry into a single intelligent feedback loop.