Get the FREE Ultimate OpenClaw Setup Guide →

sentry -rs

Fast and minimal Sentry MCP server written in Rust

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio utapyngo-sentry-mcp-rs sentry-mcp \
  --env HTTPS_PROXY="optional_https_proxy_url" \
  --env SENTRY_HOST="sentry.io" \
  --env SOCKS_PROXY="optional_socks_proxy_url" \
  --env SENTRY_AUTH_TOKEN="your_token_here"

How to use

sentry-mcp is a fast, lightweight MCP server written in Rust that provides a focused set of tools for interacting with Sentry's API. It exposes commands to retrieve issue details, trace details for distributed tracing, and to search events within an issue. Start the server using your installed binary (sentry-mcp) and configure it in your MCP client so other tools can reach it via the MCP protocol. The server is designed to be memory-efficient and easy to deploy as a single binary without runtime dependencies. Use the included environment variables to point it at your Sentry instance and provide authentication tokens as needed.

How to install

Prerequisites:

  • Rust toolchain (cargo) or prebuilt binaries from crates.io
  • Access to a Sentry API token with appropriate permissions
  • Optional: proxies configured if your environment requires them

Install from crates.io (recommended):

cargo install sentry-mcp

Install from GitHub (latest commit):

cargo install --git https://github.com/utapyngo/sentry-mcp-rs.git

Or with mise (if you prefer using mises workflow):

mise use -g github:utapyngo/sentry-mcp-rs

Verification: confirm the binary is installed as sentry-mcp and is in your PATH. Then create a minimal MCP client config to run against it.

Additional notes

Configuration tips:

  • Set SENTRY_AUTH_TOKEN and SENTRY_HOST to point at your Sentry instance. If your environment requires proxies, configure SOCKS_PROXY or HTTPS_PROXY accordingly.
  • The MCP server exposes endpoints via the MCP client configuration; ensure your client references command: "sentry-mcp" and provides required env vars.
  • If you run behind proxies or need to control network traffic, use the env vars to route requests through SOCKS/HTTPS proxies.
  • For debugging, you can run cargo build --release to ensure the binary is optimized before deployment.
  • If you encounter authentication errors, double-check token scopes and that the SENTRY_HOST is reachable from the deployment environment.

Related MCP Servers

Sponsor this space

Reach thousands of developers