Sentry Mcp Server

io.github.friendlygeorgePublished by GitHub account friendlygeorgev1.0.0Updated Oct 24, 2026

MCP server for Sentry — error tracking, issues, releases, events, and projects for AI assistants.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Connects an AI assistant to Sentry so it can browse organizations, projects, issues, events and releases, and resolve or ignore issues.

What you can do
  • List organizations, projects, teams and members with their roles and slugs
  • List issues with filters for environment, status, level, query and project, and get full issue details and grouping hashes
  • List and read events for an issue, including exception, stacktrace, breadcrumbs and tags
  • List releases and read release details with commit info and file changes
  • Resolve, ignore or unresolve an issue and optionally add a comment
When to use it
Useful when you want an assistant to triage Sentry errors during a debugging session: find unresolved production errors, pull a stack trace, check which release introduced a problem, or close issues once fixed.
Requirements
Runs locally via npx (Node.js) as a stdio process in a desktop MCP client. Requires a Sentry auth token in SENTRY_AUTH_TOKEN with scopes such as org:read, project:read, event:read, issue:read and issue:write. SENTRY_BASE_URL can point at a self-hosted Sentry instance; network access to the Sentry API is needed.
Before you install
The token grants read access to organization, project, event and issue data, and issue:write lets the assistant change issue status and post comments, so scope it narrowly and review write actions. The README also lists event:write among the scopes. The token is passed as an environment variable and should be kept out of shared config files.

Installation

In SourceWeft

  1. Open Sentry Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Sentry MCP Server

Connect AI assistants to Sentry — error tracking, issues, releases, events, and project management through the Model Context Protocol.

Works with Claude Desktop, Cursor, Windsurf, Cline, Continue, and any MCP-compatible client.

Features

ToolDescription
list_organizationsList all Sentry organizations you have access to
list_projectsList projects in an organization with slug, platform, and team info
list_issuesList issues with filters (environment, status, level, query, project)
get_issueGet full details of a specific issue — title, culprit, metadata, tags
list_issue_eventsList all events (occurrences) for a specific issue
get_eventGet full event details — exception, stacktrace, breadcrumbs, tags
list_releasesList releases in an organization with version, date, and authors
get_releaseGet details of a specific release with commit info and file changes
list_teamsList teams in an organization with member counts and slugs
list_membersList organization members with role and email
get_issue_hashesGet the grouping hashes (fingerprint) for an issue
update_issue_statusResolve, ignore, or unresolve an issue (and add a comment)

Quick Start

1. Get a Sentry Auth Token

Go to Sentry → Settings → Auth Tokens and create a token with the scopes you need (org:read, project:read, event:read, event:write, issue:read, issue:write).

Or visit: https://sentry.io/settings/auth-tokens/

2. Configure your MCP client

Claude Desktop — add to claude_desktop_config.json:

json
{  "mcpServers": {    "sentry": {      "command": "npx",      "args": ["-y", "sentry-mcp-server"],      "env": {        "SENTRY_AUTH_TOKEN": "sntrys_YOUR_TOKEN_HERE"      }    }  }}

Cursor — add to MCP settings (.cursor/mcp.json):

json
{  "mcpServers": {    "sentry": {      "command": "npx",      "args": ["-y", "sentry-mcp-server"],      "env": {        "SENTRY_AUTH_TOKEN": "sntrys_YOUR_TOKEN_HERE"      }    }  }}

3. Run manually (for testing)

bash
git clone https://github.com/friendlygeorge/sentry-mcp-server.gitcd sentry-mcp-servernpm installnpm run build
# RunSENTRY_AUTH_TOKEN=sntrys_xxx node dist/index.js

Environment Variables

VariableRequiredDefaultDescription
SENTRY_AUTH_TOKEN✅—Your Sentry auth token (sntrys_...)
SENTRY_BASE_URL❌https://sentry.io/api/0/Sentry API base URL. Override for self-hosted Sentry.

Self-hosted Sentry

If you run your own Sentry instance, set SENTRY_BASE_URL:

SENTRY_BASE_URL=https://sentry.yourcompany.com/api/0/

Example Queries

"List my Sentry organizations"

"Show me unresolved errors in the production environment for org acme project web"

"Get details of issue 1234567890 and show me the latest event's stack trace"

"Resolve issue 1234567890 and add a comment that it's fixed in v1.2.3"

"List the last 10 releases for acme"

"Who are the members of acme org and their roles?"

API Coverage

This server covers the most-used endpoints of the Sentry Web API:

  • Organizations (/organizations/)
  • Projects (/organizations/{org}/projects/)
  • Issues (/organizations/{org}/issues/, /issues/{id}/)
  • Events (/issues/{id}/events/, /projects/{org}/{project}/events/{id}/)
  • Releases (/organizations/{org}/releases/)
  • Teams (/organizations/{org}/teams/)
  • Members (/organizations/{org}/members/)

For the full Sentry API, see docs.sentry.io/api.

License

MIT © 2026 Nova

Source: README.md at commit 595a8e4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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