Skip to main content

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

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:

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 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.

Metadata

Release files for mcp-sentry 0.6.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-sentry 0.6.2
File Size Uploaded Provenance
mcp_sentry-0.6.2.tar.gz 397.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-sentry 0.6.2
File Interpreter ABI Platform
mcp_sentry-0.6.2-py3-none-any.whl Python 3 none any Details

Total release size: 404.1 kB

Release files / mcp_sentry-0.6.2.tar.gz

Download URL mcp_sentry-0.6.2.tar.gz
Size 397.4 kB
Tags Source
SHA-256 checksum
How to use checksums
fc674bdfe691a026e74553c9804b1a1382f37cf29ca87e66ceb674545b9d3b16
BLAKE2b-256 checksum
How to use checksums
e94844dab4a5ca299afb4c6fb08ea9839cb24e2199211e45f45f765bee35db50
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 6, 2025.

Transparency log

Release files / mcp_sentry-0.6.2-py3-none-any.whl

Download URL mcp_sentry-0.6.2-py3-none-any.whl
Size 6.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1b6c1be5b3fcb326b7cb1df4f6b1afba56046761e045b66b0dcfc7b35b8f9980
BLAKE2b-256 checksum
How to use checksums
fa3d604d8e3780840d4bd650ada34ec192d6d60cb93b7288d178279d013adafd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 6, 2025.

Transparency log

Security for mcp-sentry 0.6.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for mcp_sentry-0.6.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 6, 2025.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.6.2 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page