Sentry

io.github.getsentryPublished by GitHub account getsentryv0.49.0Updated Nov 7, 2026

MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Sentry's MCP server lets an AI assistant reach Sentry error monitoring, issue tracking and debugging data for sentry.io or self-hosted instances.

What you can do
  • Connect an assistant to Sentry error monitoring, issue tracking and debugging data
  • Run as a remote endpoint or as a local stdio process via npx
  • Sign in once with the auth login command, shared with the Sentry CLI, or supply an auth token
  • Manage the stored login: check status, list, switch or log out
  • Set CLI defaults and repair the local database shared with the CLI
  • Point at a self-hosted Sentry host or URL
When to use it
Useful when you want an assistant to look into Sentry errors, issues and debugging context while working, whether on sentry.io or a self-hosted Sentry instance.
Requirements
Either the remote endpoint or Node.js 22.15 or later for the npm package run through npx. Authentication is required: OAuth, a one-time auth login, or the SENTRY_AUTH_TOKEN environment variable. For self-hosted Sentry, set SENTRY_HOST or SENTRY_URL alongside the token.
Before you install
The server needs a Sentry auth token or a stored login, which grants access to your Sentry account data; each server process uses one account. The token wins over a stored login, and the deprecated SENTRY_ACCESS_TOKEN still works with a warning. The cli fix command repairs a local database shared with the Sentry CLI, so it changes local state.

Installation

In SourceWeft

  1. Open Sentry in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.getsentry%2Fsentry-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sentry": {
      "type": "http",
      "url": "https://mcp.sentry.dev/mcp"
    }
  }
}

README

@sentry/mcp-server

The Sentry MCP server for stdio clients, as a single file with no runtime dependencies. Works with sentry.io and self-hosted Sentry.

json
{  "command": "npx",  "args": ["-y", "@sentry/mcp-server@latest"]}

Requires Node.js 22.15 or later.

Authentication

  • npx -y @sentry/mcp-server auth login signs in once. The login is shared with the sentry CLI, so an existing sentry auth login works too.

  • To use a token instead, set SENTRY_AUTH_TOKEN in the client's env. It wins over a stored login:

    json
    {  "command": "npx",  "args": ["-y", "@sentry/mcp-server@latest"],  "env": {    "SENTRY_AUTH_TOKEN": "sntryu_..."  }}

  • --access-token / SENTRY_ACCESS_TOKEN are deprecated. They still work, as SENTRY_AUTH_TOKEN, and print a warning on stderr.

  • Each server process uses one account. The package runs the CLI's own auth commands, so npx -y @sentry/mcp-server auth status|list|switch|logout manages the same login.

  • npx -y @sentry/mcp-server cli defaults and cli fix are the CLI's own commands too: they set the defaults (such as ca-cert for a corporate TLS proxy) and repair the local database the server shares with the CLI.

Options

Starting the server is the default command, so npx -y @sentry/mcp-server and npx -y @sentry/mcp-server mcp are the same. Run npx -y @sentry/mcp-server mcp --help for the flags and environment variables. For self-hosted Sentry, set SENTRY_HOST / SENTRY_URL (with SENTRY_AUTH_TOKEN, only these scope the token to your server). See stdio authentication.

Development

The source lives in packages/cli: packages/cli/src/mcp-server.ts runs the CLI's runner with an application of four commands, mcp, auth, cli (defaults and fix only), and help (packages/cli/src/mcp-server-app.ts). pnpm run bundle builds dist/sentry-mcp.cjs from it, and pnpm run test:bundle smoke-tests the result.

Source: packages/mcp-server/README.md at commit b3495bd

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v0.49.0LatestNov 7, 2026
  2. v0.48.0Nov 6, 2026
  3. v0.42.0Sep 25, 2026
  4. v0.41.0Sep 25, 2026
  5. v0.40.0Sep 25, 2026
  6. v0.25.0Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.