# utapyngo/sentry-mcp-rs [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/utapyngo/sentry-mcp-rs  
**GitHub Stars:** 9  
**npm Downloads (last month):** 136  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/utapyngo-sentry-mcp-rs

## Description
Fast and minimal Sentry MCP server written in Rust

## Tools
Capabilities this server exposes over MCP:

- **issue_url** — Full Sentry issue URL (alternative to the parameters below)
- **organization_slug** — Organization slug (required if `issue_url` not provided)
- **issue_id** — Issue ID like `PROJECT-123` or numeric ID (required if `issue_url` not provided)
- **event_id** — Specific event ID to fetch instead of latest (optional)
- **trace_id** — 32-character hex trace ID
- **query** — Optional Sentry search query
- **limit** — Maximum events to return (default: 10, max: 100)
- **sort** — Sort order: `newest` (default) or `oldest`

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sentry-mcp-rs": {
    "command": "npx",
    "args": ["-y","@modelcontextprotocol/inspector"],
    "env": {
      "SENTRY_AUTH_TOKEN": "",
      "SENTRY_HOST": "",
      "SOCKS_PROXY": "",
      "HTTPS_PROXY": ""
    }
  }
}
```

**Requires environment variables:** `SENTRY_AUTH_TOKEN`, `SENTRY_HOST`, `SOCKS_PROXY`, `HTTPS_PROXY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What utapyngo/sentry-mcp-rs MCP server does

utapyngo/sentry-mcp-rs MCP server connects an MCP client to a Sentry instance and exposes a focused set of read-oriented investigation tools. It is implemented in Rust and distributed as the `sentry-mcp` binary, with installation available through crates.io, GitHub, or mise.

The server provides three capabilities:

- `get_issue_details` retrieves information for a Sentry issue, including metadata, tags, and stack traces. A specific event can be selected; otherwise, the tool can retrieve the latest event.
- `get_trace_details` returns trace information for distributed tracing analysis, including the span tree and timing data.
- `search_issue_events` searches events belonging to an issue using Sentry’s query syntax and supports result limits and ordering.

## How it works

The MCP client starts the local `sentry-mcp` executable over its configured command interface. The server uses `SENTRY_AUTH_TOKEN` for Sentry API authentication and `SENTRY_HOST` to identify the Sentry instance, such as `sentry.io` or a self-hosted hostname.

Issue detail requests may provide a complete Sentry issue URL. Alternatively, they require an organization slug and issue ID, which may be a project-style identifier such as `PROJECT-123` or a numeric ID. An optional event ID selects a particular event instead of the latest one.

Trace requests require an organization slug and a 32-character hexadecimal trace ID. Event searches require an organization slug and issue ID; they can also accept a Sentry query, a maximum result count, and either newest-first or oldest-first ordering. The default event limit is 10, and the maximum is 100.

## Setup and configuration

Install the binary from crates.io with:

```bash
cargo install sentry-mcp
```

After installation, configure the MCP client to run `sentry-mcp` and provide the required environment variables:

```json
{
  "mcpServers": {
    "sentry": {
      "command": "sentry-mcp",
      "env": {
        "SENTRY_AUTH_TOKEN": "your_token_here",
        "SENTRY_HOST": "sentry.io"
      }
    }
  }
}
```

utapyngo/sentry-mcp-rs MCP server also accepts `SOCKS_PROXY` for a SOCKS5 proxy and `HTTPS_PROXY` for an HTTPS proxy. The README documents mise-based installation and a GitHub source installation as alternatives to cargo.

## Tools and capabilities

The available tool inputs are deliberately centered on Sentry investigation:

- Resolve an issue by URL or organization and issue ID.
- Fetch a selected issue event or use the latest event.
- Inspect distributed trace spans and timing.
- Filter issue events with Sentry search syntax.
- Set event result count from the default of 10 up to 100.
- Choose `newest` or `oldest` event ordering.

## Limitations and notes

utapyngo/sentry-mcp-rs MCP server requires an existing Sentry API authentication token and a configured Sentry hostname. The supplied material documents retrieval, inspection, and search operations; it does not describe tools for modifying issues, events, traces, or Sentry configuration.

The trace tool requires a valid 32-character hexadecimal trace ID. For issue details, either a full issue URL or both the organization slug and issue ID must be supplied. Search operations similarly require an organization slug and issue ID.

The project is licensed under MIT. Its README describes a single-binary Rust distribution with no runtime dependencies, but client compatibility is not specified for particular MCP applications.

_Full upstream README: https://allmcps.com/mcp/utapyngo-sentry-mcp-rs/readme_