MCP.so
Sign In
S

Sentry

@javaDer

Repository

About Sentry

No overview available yet

#mcp-sentry#sentry-server#error-analysis

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "sentry": {
      "command": "uvx",
      "args": [
        "mcp-sentry-custom",
        "--auth-token",
        "YOUR_SENTRY_TOKEN",
        "--project-slug",
        "YOUR_PROJECT_SLUG",
        "--organization-slug",
        "YOUR_ORGANIZATION_SLUG",
        "--sentry-url",
        "YOUR_SENTRY_URL"
      ]
    }
  }
}

Tools

2

Retrieve and analyze a Sentry issue by ID or URL. Use this tool when you need to: - Investigate production errors and crashes - Access detailed stacktraces from Sentry - Analyze error patterns and frequencies - Get information about when issues first/last occurred - Review error counts and status

Retrieve and analyze Sentry issues by project slug. Use this tool when you need to: - Investigate production errors and crashes - Access detailed stacktraces from Sentry - Analyze error patterns and frequencies - Get information about when issues first/last occurred - Review error counts and status

Overview

What is Sentry?

Sentry is an MCP server that retrieves and analyzes issues from Sentry.io or self-hosted Sentry instances. It provides tools to inspect error reports, stack traces, and other debugging information directly from your Sentry account.

How to use Sentry?

Install the server via Smithery, uv, pip, or Docker. Configure it with your Sentry authentication token, project slug, organization slug, and Sentry URL. Use it with Claude Desktop or Zed by adding the appropriate configuration to claude_desktop_config.json or Zed's settings.json.

Key features of Sentry

  • Retrieve a specific Sentry issue by ID or URL
  • List all issues for a given project and organization
  • Detailed issue information including stack trace and event count
  • Formatted issue details via a prompt for conversation context
  • Supports both Sentry.io and self‑hosted Sentry instances
  • Compatible with multiple MCP clients (Claude Desktop, Zed)

Use cases of Sentry

  • Debug an application error by fetching its full stack trace from Sentry
  • Quickly review recent issues in a project during a development session
  • Integrate Sentry issue details into an AI assistant’s conversation context
  • Automate issue triage by pulling structured data into an MCP‑enabled tool

FAQ from Sentry

What does Sentry require to run?

You need a Sentry authentication token, a project slug, an organization slug, and the URL of your Sentry instance (either Sentry.io or self‑hosted). The server can be run via uvx, pip, or Docker.

How do I install Sentry?

Install via Smithery (npx -y @smithery/cli install @javaDer/mcp-sentry-custom), run directly with uvx, install via pip, or use a Docker container. All methods are documented in the README.

Where does Sentry store my data?

Sentry does not store any data locally; it retrieves issue information directly from your Sentry account (Sentry.io or self‑hosted) each time you use it.

What transport or authentication does Sentry use?

Sentry uses standard MCP transport (stdio). Authentication is handled via the provided --auth-token parameter. No OAuth or additional auth flows are documented.

Are there any known limits or restrictions?

The README does not mention any specific limits. It is a fork of the official sentry server from the modelcontextprotocol/servers repository.

Frequently asked questions

What does Sentry require to run?

You need a Sentry authentication token, a project slug, an organization slug, and the URL of your Sentry instance (either Sentry.io or self‑hosted). The server can be run via `uvx`, `pip`, or Docker.

How do I install Sentry?

Install via Smithery (`npx -y @smithery/cli install @javaDer/mcp-sentry-custom`), run directly with `uvx`, install via `pip`, or use a Docker container. All methods are documented in the README.

Where does Sentry store my data?

Sentry does not store any data locally; it retrieves issue information directly from your Sentry account (Sentry.io or self‑hosted) each time you use it.

What transport or authentication does Sentry use?

Sentry uses standard MCP transport (stdio). Authentication is handled via the provided `--auth-token` parameter. No OAuth or additional auth flows are documented.

Are there any known limits or restrictions?

The README does not mention any specific limits. It is a fork of the official `sentry` server from the modelcontextprotocol/servers repository.

Comments

Basic information

Category

Developer Tools

Transports

stdio

Author

javaDer

Submitted by

Mac Jack Jack

More Developer Tools MCP servers

ZeroBeacon — 1000-Tool Collision-Proof Commerce Router

DavidFox998

ZeroBeacon.ai — Collision-proof commerce router for AI agents. 1000 MCP tools: commerce, trust, billing, sovereign ID + everyday tools. LIVE.

Raccha AI

Shree Mandadi

MCP-first toolbox for agents: namespaced key-value storage, a FIFO queue, auth, and a handful of stateless utility tools (JWT decode, hashing, cert inspection, CIDR math). Free while in early access. This repository is a

ship.page

Bitgate

Throw HTML at an API, get an unguessable URL back. Zero-config remote MCP server — your agent deploys pages, sites and CI reports in one call. Free, no signup needed.

Moxie Docs

Jackalope-Dev

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

1

BetterBugs

BetterBugs

The BetterBugs MCP (Model Context Protocol) enables you to load BetterBugs bug reports (via report links) directly to your preferred AI Agents and developer environments with MCP Client capabilities (such as Cursor, VS C