Skip to main content
Glama
Sentry MCP Server

Sentry MCP Server

Sentry MCP Server

@zereight/sentry-server

Sentry MCP(Model Context Protocol) Server. Allows interaction with the Sentry API to fetch issue and event details.

Related MCP server: Sentry

Usage

Using with Claude, Roo Code, Cline, etc.

Add the following configuration to your MCP settings file (e.g., mcp_settings.json):

{
  "mcpServers": {
    "sentry-server-npm": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/sentry-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "YOUR_SENTRY_AUTH_TOKEN", // Required
        "SENTRY_ORG_SLUG": "YOUR_ORG_SLUG",         // Required: Your Sentry organization slug
        "SENTRY_PROJECT_NAMES": "YOUR_PROJECT1,YOUR_PROJECT2", // Required: Comma-separated Sentry project slugs
        "SENTRY_BASE_URL": "YOUR_SENTRY_BASE_URL"   // Optional: Defaults to https://sentry.io
      },
      "disabled": false
    }
  }
}

Replace placeholder values like "YOUR_SENTRY_AUTH_TOKEN", "YOUR_ORG_SLUG", and "YOUR_PROJECT1,YOUR_PROJECT2" with your actual Sentry details. Provide project slugs separated by commas. Project slugs are used in Sentry URLs (e.g., https://<org-slug>.sentry.io/settings/projects/<project-slug>/). Auth tokens can be generated in User Settings > Auth Tokens.

Using with Cursor (or direct CLI)

When using with Cursor or running directly, you can set up environment variables and run the server as follows:

env SENTRY_AUTH_TOKEN=YOUR_SENTRY_AUTH_TOKEN \
    SENTRY_ORG_SLUG=YOUR_ORG_SLUG \
    SENTRY_PROJECT_NAMES=YOUR_PROJECT1,YOUR_PROJECT2 \
    SENTRY_BASE_URL=YOUR_SENTRY_BASE_URL \
    npx @zereight/sentry-server
  • SENTRY_AUTH_TOKEN (Required): Your Sentry authentication token.

  • SENTRY_ORG_SLUG (Required): The slug of your Sentry organization.

  • SENTRY_PROJECT_NAMES (Required): Comma-separated names (slugs) of your Sentry projects.

  • SENTRY_BASE_URL (Optional): The base URL for your Sentry instance (e.g., for self-hosted). Defaults to https://sentry.io.

Tools ๐Ÿ› ๏ธ

  1. get_sentry_issue

    • Fetches details for a specific Sentry issue. โ„น๏ธ

    • Inputs:

      • issue_id_or_url (string, required): The Sentry issue ID or the full URL of the issue page.

    • Returns: Detailed information about the issue (JSON string).

  2. list_organization_projects

    • Lists all projects for the configured Sentry organization. ๐Ÿ“‚

    • Inputs: None

    • Returns: A list of project objects (JSON string).

  3. list_project_issues

    • Lists issues for a specific project, with optional filtering. ๐Ÿ›

    • Inputs:

      • organization_slug (string, optional): The slug of the organization. Defaults to SENTRY_ORG_SLUG env var.

      • project_slug (string, required): The slug of the project to list issues for.

      • query (string, optional): Sentry search query to filter issues (e.g., "is:unresolved", "assignee:me").

      • statsPeriod (string, optional): Time period for statistics (e.g., "24h", "14d", "auto").

      • cursor (string, optional): Pagination cursor for fetching next/previous page.

    • Returns: A list of issue objects and pagination information (JSON string).

  4. get_event_details

    • Gets details for a specific event within a project. ๐Ÿ“„

    • Inputs:

      • organization_slug (string, optional): The slug of the organization. Defaults to SENTRY_ORG_SLUG env var.

      • project_slug (string, required): The slug of the project the event belongs to.

      • event_id (string, required): The ID of the event to retrieve.

    • Returns: Detailed information about the specific event (JSON string).

Environment Variable Configuration

Before running the server, you must set the following environment variables:

SENTRY_AUTH_TOKEN=YOUR_SENTRY_AUTH_TOKEN
SENTRY_ORG_SLUG=YOUR_ORG_SLUG
SENTRY_PROJECT_NAMES=YOUR_PROJECT_NAME1,YOUR_PROJECT_NAME2

Optionally, you can also set:

SENTRY_BASE_URL=YOUR_SENTRY_BASE_URL # Default: https://sentry.io

The Inspector will provide a URL to access debugging tools in your browser.

License

MIT License

Available Tools

4 tools
get_event_detailsC

Get details for a specific event within a project.

Inputs: project_slug (required), event_id (required), organization_slug.

get_sentry_issueC

Get details for a specific Sentry issue using its ID or URL

Inputs: issue_id_or_url (required).

list_organization_projectsB

List all projects for the configured Sentry organization

Inputs: no named parameters.

list_project_issuesC

List issues for a specific project, with optional filtering.

Inputs: project_slug (required), organization_slug, query, statsPeriod, +1 more.

Tool Schema Changelog

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

Loading tool schema changelogโ€ฆ

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools have mostly distinct purposes: get_event_details and get_sentry_issue both retrieve details but target different resources (events vs. issues), while list_organization_projects and list_project_issues handle listing operations for different scopes. There is minor potential confusion between the two 'get' tools since both fetch details, but their descriptions clarify the resource distinction.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_event_details, list_organization_projects) with clear, descriptive naming. There are no deviations in style or convention across the set.

    Tool Count3/5

    With only 4 tools, the server feels somewhat thin for a Sentry integration, which typically involves more operations like creating issues, updating statuses, or managing alerts. While the tools cover basic read and list functions, the count is borderline low for the domain's scope.

    Completeness2/5

    The toolset is significantly incomplete for a Sentry server, lacking essential operations such as creating or updating issues, resolving events, or managing project settings. It only supports read and list functions, leaving major gaps in CRUD coverage that will hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Sentry's error tracking and monitoring tools through a unified API, allowing natural language access to Sentry services.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to retrieve and analyze Sentry issues, including error reports, stacktraces, and debugging information from Sentry.io.
      10 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Sentry organizations, projects, and issues directly from MCP clients like Claude Code.
      18 npm
      MIT