MCP HubMCP Hub
MCP-100

mcp-sentry

by: MCP-100

A Model Context Protocol server for retrieving and analyzing issues from Sentry.io

13created 05/03/2025
Visit
Sentry
analytics

📌Overview

Purpose: To provide a Model Context Protocol server that facilitates the retrieval and analysis of issues from Sentry.io, aiding in error inspection and debugging.

Overview: mcp-sentry enables users to connect with their Sentry accounts and access critical error reports and debugging information, offering a comprehensive set of tools for issue analysis in real-time.

Key Features:

  • Feature 1: get_sentry_issue
    Allows users to retrieve and analyze a specific Sentry issue by ID or URL, returning detailed information such as title, status, timestamps, and stacktrace to aid in debugging.

  • Feature 2: get_list_issues
    Facilitates the retrieval of lists of issues within a specific Sentry project, providing insights into multiple issues' statuses and timestamps to streamline project management and error tracking.


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

Installation

Installing via Smithery

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

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

Using uv (recommended)

When using uv no specific installation is needed. 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:

Using uvx
"mcpServers": {
  "sentry": {
    "command": "uvx",
    "args": ["mcp-sentry", "--auth-token", "YOUR_SENTRY_TOKEN","--project-slug" ,"YOUR_PROJECT_SLUG", "--organization-slug","YOUR_ORGANIZATION_SLUG"]
  }
}
Using docker
"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"]
  }
}
Using pip installation
"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:

Using uvx
"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"]
    }
  }
],
Using pip installation
"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"]
  }
},
Using pip installation with custom path
"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:

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

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.