Sentry MCP server

Sentry × VS Code

Use the Sentry MCP server
in VS Code

Query issues, releases, and errors across your Sentry projects — straight from your AI. This guide connects Sentry to VS Code (GitHub Copilot's agent mode) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · OAuth sign-in

Setup: Sentry in VS Code

VS Code adds MCP servers via MCP server configuration. The gateway route takes about two minutes:

  1. Connect Sentry to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to VS Code' — VS Code prompts to add the gateway as an HTTP MCP server.
  3. Confirm and approve the sign-in.
  4. Copilot's agent mode can now use Sentry — logged and governed through your gateway.

What to ask once it’s connected

Which issues spiked after yesterday's release?
Summarize the top unresolved errors in the checkout flow.
Find the release that introduced this regression.
Draft a post-mortem from the timeline of issue #4132.

Why route it through a gateway

One URL, every client

The same Sentry connection works in Claude, Claude Code, ChatGPT, Cursor too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Sentry exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything VS Code did with Sentry — searchable, exportable, auditable.

Scanned and probed

Sentry passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Sentry in Claude · Sentry in Claude Code · Sentry in ChatGPT · Sentry in Cursor