sentry-selfhosted-mcp

sentry-selfhosted-mcp

By ddfourtwo GitHub

An MCP server for self-hosted sentry.

sentry self-hosted
Overview

What is Sentry Self-Hosted MCP?

Sentry Self-Hosted MCP is a Model Context Protocol server designed for interacting with self-hosted Sentry instances, allowing users to manage and retrieve information about issues within their Sentry setup.

How to use Sentry Self-Hosted MCP?

To use the server, clone the repository, install the dependencies, and configure the necessary environment variables for your Sentry instance. Then, run the server to interact with your Sentry projects and issues.

Key features of Sentry Self-Hosted MCP?

  • Retrieve details for specific Sentry issues by ID or URL.
  • List all projects within a configured Sentry organization.
  • Filter and list issues for specific projects based on query or status.
  • Update the status of Sentry issues.
  • Add comments to Sentry issues.

Use cases of Sentry Self-Hosted MCP?

  1. Managing and tracking issues in self-hosted Sentry instances.
  2. Automating the retrieval of issue details for reporting.
  3. Facilitating team collaboration by commenting on issues directly.

FAQ from Sentry Self-Hosted MCP?

  • What is required to run the server?

You need to set environment variables for SENTRY_URL, SENTRY_AUTH_TOKEN, and SENTRY_ORG_SLUG to connect to your Sentry instance.

  • Is there a specific programming language used?

Yes, the server is built using JavaScript and requires Node.js for execution.

  • Can I customize the server's functionality?

Yes, you can modify the source code to add or change features as per your requirements.

Content

sentry-selfhosted-mcp

A Model Context Protocol (MCP) server designed specifically for interacting with self-hosted Sentry instances.

Overview

This server provides tools to retrieve information and perform actions on issues within a self-hosted Sentry setup. It reads the Sentry instance URL, authentication token, and organization slug from environment variables.

Available Tools

The following tools are available:

  1. get_sentry_issue

  2. list_sentry_projects

    • Description: List all projects within the configured Sentry organization.
    • Input: {} (No arguments needed)

  3. list_sentry_issues

    • Description: List issues for a specific project, optionally filtering by query or status.
    • Input: { "project_slug": "string", "query": "string" (optional), "status": "resolved" | "unresolved" | "ignored" (optional) }

  4. get_sentry_event_details

    • Description: Retrieve details for a specific event ID within a project.
    • Input: { "project_slug": "string", "event_id": "string" }

  5. update_sentry_issue_status

    • Description: Update the status of a Sentry issue.
    • Input: { "issue_id": "string", "status": "resolved" | "ignored" | "unresolved" }

  6. create_sentry_issue_comment

    • Description: Add a comment to a Sentry issue.
    • Input: { "issue_id": "string", "comment_text": "string" }

Installation & Setup

  1. Clone/Place Project: Clone this repository or place the project files in your desired location.
  2. Install Dependencies: Navigate into the project directory (sentry-selfhosted-mcp) and run: 
    cd <path/to/sentry-selfhosted-mcp>
npm install
  3. Build Server: Compile the TypeScript code from the project directory: 
    npm run build
    This creates the executable JavaScript file in the build/ directory.

Configuration

This server requires the following environment variables to be set:

  • SENTRY_URL: The base URL of your self-hosted Sentry instance (e.g., https://sentry.beoflow.app).
  • SENTRY_AUTH_TOKEN: Your Sentry API authentication token (ensure it has necessary scopes like issue:read, project:read, event:read, issue:write, comment:write).
  • SENTRY_ORG_SLUG: The slug of your Sentry organization (e.g., beoflow).

Example MCP Client Configuration:

Add the following entry to your MCP client's configuration file (e.g., cline_mcp_settings.json for the VS Code extension, claude_desktop_config.json for Claude.app):

    "sentry-selfhosted-mcp": {
      "command": "node",
      "args": [
        "<full/path/to/sentry-selfhosted-mcp/build/index.js>"
      ],
      "env": {
        "SENTRY_URL": "YOUR_SENTRY_URL",
        "SENTRY_AUTH_TOKEN": "YOUR_SENTRY_AUTH_TOKEN",
        "SENTRY_ORG_SLUG": "YOUR_SENTRY_ORG_SLUG"
      },
      "disabled": false,
      "autoApprove": [],
      "transportType": "stdio"
    }

Replace YOUR_SENTRY_URL, YOUR_SENTRY_AUTH_TOKEN, and YOUR_SENTRY_ORG_SLUG with your actual values.

After updating the settings file, the MCP client should automatically connect to the server.

No tools information available.
Sentry
Sentry by modelcontextprotocol

Retrieving and analyzing issues from Sentry.io

sentry error-tracking
View Details