Skip to main content
Glama
Sign In
sentry-mcp-server

sentry-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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

Tool

Description

list_organizations

List all Sentry organizations you have access to

list_projects

List projects in an organization with slug, platform, and team info

list_issues

List issues with filters (environment, status, level, query, project)

get_issue

Get full details of a specific issue — title, culprit, metadata, tags

list_issue_events

List all events (occurrences) for a specific issue

get_event

Get full event details — exception, stacktrace, breadcrumbs, tags

list_releases

List releases in an organization with version, date, and authors

get_release

Get details of a specific release with commit info and file changes

list_teams

List teams in an organization with member counts and slugs

list_members

List organization members with role and email

get_issue_hashes

Get the grouping hashes (fingerprint) for an issue

update_issue_status

Resolve, ignore, or unresolve an issue (and add a comment)

Related MCP server: Sentry MCP Server

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:

{
  "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):

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

3. Run manually (for testing)

git clone https://github.com/friendlygeorge/sentry-mcp-server.git
cd sentry-mcp-server
npm install
npm run build

# Run
SENTRY_AUTH_TOKEN=sntrys_xxx node dist/index.js

Environment Variables

Variable

Required

Default

Description

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

Available Tools

12 tools
get_eventA

Get full details of a specific event by its ID, including exception values, stack trace, breadcrumbs, tags, and request context. Use this to debug a specific occurrence.

Inputs: org (required), project (required), event_id (required).

get_issueA

Get full details of a specific issue by numeric ID, including title, culprit, metadata, tags, firstSeen, lastSeen, count, and project info.

Inputs: issue_id (required).

get_issue_hashesA

Get the grouping hashes (fingerprint) for a specific issue. Useful to identify why issues are grouped together or to deduplicate across projects.

Inputs: issue_id (required).

get_releaseA

Get details of a specific release by version, including commit info, last commit, first/last event, deploy count, new issues, and associated projects.

Inputs: org (required), version (required).

list_issue_eventsA

List all events (individual occurrences) for a specific issue. Returns event id, message, platform, dateCreated, and tags. Use to find the most recent occurrence.

Inputs: issue_id (required), cursor.

list_issuesA

List issues in an organization with optional filters. An issue is a unique error grouped by fingerprint. Returns id, title, level, status, lastSeen, firstSeen, count, and project info.

Inputs: org (required), sort, level, limit, +5 more.

list_membersB

List members of a Sentry organization. Returns user id, email, name, role, and org role info.

Inputs: org (required), cursor.

list_organizationsA

List all Sentry organizations the authenticated user has access to. Returns id, slug, name, and status for each organization.

Inputs: cursor.

list_projectsA

List all projects in a Sentry organization. Returns project slug, name, platform, id, and team assignments.

Inputs: org (required), cursor.

list_releasesA

List releases in a Sentry organization. Returns version, name, dateReleased, dateCreated, newGroups, and authors for each release.

Inputs: org (required), limit, query, cursor.

list_teamsB

List teams in a Sentry organization. Returns team id, slug, name, memberCount, and isMember.

Inputs: org (required), cursor.

update_issue_statusA

Change the status of a Sentry issue — resolve it, mark it unresolved, ignore it, or set a resolution in the next release. Optionally attach a comment.

Inputs: status (required), issue_id (required), comment.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: list_* for listing entities, get_* for retrieving single entities, update_issue_status for modifying an issue, and get_event/list_issue_events for event-level detail. Even closely related tools like list_issues and get_issue are clearly differentiated by summary vs. full detail.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_organizations, get_release, update_issue_status). Compound nouns like get_issue_hashes and list_issue_events still use the same prefixes and remain predictable.

    Tool Count5/5

    12 tools is well-scoped for a Sentry server, covering the core resources (organizations, projects, issues, events, releases, teams, members) without redundancy or bloat. Each tool serves a clear purpose in the domain.

    Completeness4/5

    The surface covers list/get for all major entities and provides an issue status update action, which is the primary write operation in Sentry. Minor gaps like no get_project or get_organization are negligible because list_projects and list_organizations return sufficient detail, but there is no way to update other resources.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • MCP Sentry

      MCP-100
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.
      2
      23
      -

    • Sentry MCP Server

      codyde
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Sentry for error tracking and monitoring, allowing retrieval and analysis of error data, project management, and performance monitoring through the Sentry API.
      11
      21
      ISC
    • Sentry MCP Server

      Sentry MCP Serverofficial

      getsentry
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that lets AI assistants interact with the Sentry API to retrieve and analyze error data, manage projects, and monitor application performance.
      11
      12
      ISC

    • Sentry MCP Server

      zereight
      F
      license
      B
      quality
      D
      maintenance
      Enables interaction with Sentry's error tracking platform to fetch and manage issue details, events, and project information through the Sentry API.
      4
      34 npm
      1
      -