Sentry Integration MCP Server

Enables AI models to query and analyze error reports and events from Sentry.

Local serverstdioTypeScript

What is the Sentry Integration MCP server?

Most monitoring and observability work still happens through a UI a human drives. Sentry Integration MCP server moves it into the conversation instead. Enables AI models to query and analyze error reports and events from Sentry.

The short version

This is a Model Context Protocol (MCP) server implemented in TypeScript for connecting to the Sentry error tracking service. This server allows AI models to query and analyze error reports and events on Sentry.

  • Retrieves and analyzes Sentry issues by ID or URL
  • issue_id_or_url (string): Sentry issue ID or URL to analyze
  • Returns: Issue details including:
  • First seen timestamp
  • Last seen timestamp
  • Complete stack trace

Getting it running

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Input — * issue_id_or_url (string): Sentry issue ID or URL to analyze
  • Returns — Issue details including:

What it needs from you

Configuration is passed through the environment: SENTRY_AUTH_TOKEN, SENTRY_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sentry Integration's toolset — Input, Returns — is a fair guide to whether it matches your workflow. It is maintained by Zzzccs123; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Input* issue_id_or_url (string): Sentry issue ID or URL to analyze
ReturnsIssue details including:

How to install the Sentry Integration MCP server

{
  "mcpServers": {
    "sentry-integration": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "SENTRY_AUTH_TOKEN": "your-value",
        "SENTRY_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SENTRY_AUTH_TOKENCredential the server authenticates with.Yes
SENTRY_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Sentry Integration to Input.
  • Use Sentry Integration to Returns.

Frequently asked questions

No, providing the complete Sentry issue URL will automatically extract the necessary project and organization information. You can omit those env variables if the URL contains the details.