Skip to main content
Glama
mcp-sentry

mcp-sentry

by fastmcp-me

Add to Cursor Add to VS Code Add to Claude Add to ChatGPT Add to Codex Add to Gemini

mcp-sentry: A Sentry MCP server

Overview

A Model Context Protocol server for retrieving and analyzing issues from Sentry.io. This server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account.

Tools

  1. get_sentry_issue

    • Retrieve and analyze a Sentry issue by ID or URL

    • Input:

      • issue_id_or_url (string): Sentry issue ID or URL to analyze

    • Returns: Issue details including:

      • Title

      • Issue ID

      • Status

      • Level

      • First seen timestamp

      • Last seen timestamp

      • Event count

      • Full stacktrace

  2. get_list_issues

    • Retrieve and analyze Sentry issues by project slug

    • Input:

      • project_slug (string): Sentry project slug to analyze

      • organization_slug (string): Sentry organization slug to analyze

    • Returns: List of issues with details including:

      • Title

      • Issue ID

      • Status

      • Level

      • First seen timestamp

      • Last seen timestamp

      • Event count

      • Basic issue information

Prompts

  1. sentry-issue

    • Retrieve issue details from Sentry

    • Input:

      • issue_id_or_url (string): Sentry issue ID or URL

    • Returns: Formatted issue details as conversation context

Related MCP server: Sentry MCP Server

Installation

Installing via Smithery

To install mcp-sentry for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @qianniuspace/mcp-sentry --client claude

When using uv no specific installation is needed. We will use uvx to directly run mcp-sentry.

Using PIP

Alternatively you can install mcp-sentry via pip:

pip install mcp-sentry

or use uv

uv pip install -e .

After installation, you can run it as a script using:

python -m mcp_sentry

Configuration

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

"mcpServers": {
  "sentry": {
    "command": "uvx",
    "args": ["mcp-sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
  }
}
"mcpServers": {
  "sentry": {
    "command": "docker",
    "args": ["run", "-i", "--rm", "mcp/sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
  }
}
"mcpServers": {
  "sentry": {
    "command": "python",
    "args": ["-m", "mcp_sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
  }
}

Usage with Zed

Add to your Zed settings.json:

For Example Curson mcp.json

"context_servers": [
  "mcp-sentry": {
    "command": {
      "path": "uvx",
      "args": ["mcp-sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
    }
  }
],
"context_servers": {
  "mcp-sentry": {
    "command": "python",
    "args": ["-m", "mcp_sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
  }
},
"context_servers": {
  "sentry": {
      "command": "python",
      "args": [
        "-m",
        "mcp_sentry",
        "--auth-token",
        "YOUR_SENTRY_TOKEN",
        "--project-slug",
        "YOUR_PROJECT_SLUG",
        "--organization-slug",
        "YOUR_ORGANIZATION_SLUG"
      ],
      "env": {
        "PYTHONPATH": "path/to/mcp-sentry/src"
      }
    }
},

Debugging

You can use the MCP inspector to debug the server. For uvx installations:

npx @modelcontextprotocol/inspector uvx mcp-sentry --auth-token YOUR_SENTRY_TOKEN --project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG

Or if you've installed the package in a specific directory or are developing on it:

cd path/to/servers/src/sentry
npx @modelcontextprotocol/inspector uv run mcp-sentry --auth-token YOUR_SENTRY_TOKEN --project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG  

or in term

npx @modelcontextprotocol/inspector uv --directory /Volumes/ExtremeSSD/MCP/mcp-sentry/src run mcp_sentry --auth-token YOUR_SENTRY_TOKEN
--project-slug YOUR_PROJECT_SLUG --organization-slug YOUR_ORGANIZATION_SLUG

Inspector-tools

Fork From

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

2 tools
get_list_issuesA

Retrieve and analyze Sentry issues by project slug. Use this tool when you need to: - Investigate production errors and crashes - Access detailed stacktraces from Sentry - Analyze error patterns and frequencies - Get information about when issues first/last occurred - Review error counts and status

Inputs: project_slug, organization_slug.

get_sentry_issueA

Retrieve and analyze a Sentry issue by ID or URL. Use this tool when you need to: - Investigate production errors and crashes - Access detailed stacktraces from Sentry - Analyze error patterns and frequencies - Get information about when issues first/last occurred - Review error counts and status

Inputs: issue_id_or_url (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 2 tools

    Disambiguation2/5

    Both tools have nearly identical descriptions, both involving retrieving and analyzing Sentry issues. The only difference is the input parameter (project slug vs ID/URL), but the overlapping purpose and identical phrasing make it unclear which tool to use in a given scenario.

    Naming Consistency4/5

    Both tools follow a 'get_' prefix with snake_case, which is consistent. However, the first tool name 'get_list_issues' is slightly awkward (could be 'get_issues_by_project') but still fits the pattern. Minor deviation from ideal naming.

    Tool Count3/5

    With only 2 tools, the server feels underdeveloped for a comprehensive Sentry integration. While the scope is focused on retrieval, additional tools for updating or managing issues are expected. The count is borderline but not extremely low.

    Completeness2/5

    The tool set only covers retrieving issues by project or ID. Missing operations like updating issue status, assigning, or searching across projects create significant gaps that would hinder an agent from performing typical Sentry workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      -
    • 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
      A TypeScript implementation of a Model Context Protocol server that connects to Sentry error tracking service, allowing AI models to query and analyze error reports and events.
      MIT