topmcps
Browse MCPs
Sentry

Sentry

Official

Triage errors, inspect traces, and query events from Sentry.

Score 85(?)SentryApache-2.0650Verified Top MCPs for Security →
InstallView on GitHub

Install Sentry

— pick your client, copy, paste.
claude_desktop_config.json
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.json
# export SENTRY_AUTH_TOKEN=sntrys_your_token
# export SENTRY_ORG=your-org-slug
claude mcp add sentry -- npx -y @sentry/mcp-server

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.json
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.json
{
  "servers": {
    "sentry": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.json
{
  "mcpServers": {
    "sentry": {
      "command": "npx",
      "args": [
        "-y",
        "@sentry/mcp-server"
      ],
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@sentry/mcp-server"
          ],
          "env": {
            "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
            "SENTRY_ORG": "${SENTRY_ORG}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.toml
# ~/.codex/config.toml
[mcp_servers.sentry]
command = "npx"
args = [
  "-y",
  "@sentry/mcp-server",
]
env = { SENTRY_AUTH_TOKEN = "${SENTRY_AUTH_TOKEN}", SENTRY_ORG = "${SENTRY_ORG}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.json
{
  "context_servers": {
    "sentry": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@sentry/mcp-server"
        ]
      },
      "env": {
        "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
        "SENTRY_ORG": "${SENTRY_ORG}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Settings → Connectors → Developer mode
{
  "name": "Sentry",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@sentry/mcp-server"
  ],
  "env": {
    "SENTRY_AUTH_TOKEN": "${SENTRY_AUTH_TOKEN}",
    "SENTRY_ORG": "${SENTRY_ORG}"
  }
}

Enable Developer mode (paid plans) and enter these values in the UI.

Quick answer

What it does

Exposes Sentry's issue, event, and project APIs as tools — list issues, read traces and breadcrumbs, search events, and post comments or assign.

Best for

  • Incident triage
  • On-call assistance
  • Error-trend summaries
  • Post-deploy regression checks

Not for

  • Paging workflows
  • Metric dashboarding (use a dedicated BI MCP)

Setup recipe

  1. 1

    Install

    Copy the install snippet for your client from the Install section above.

  2. 2

    Set required secrets

    Set SENTRY_AUTH_TOKEN, SENTRY_ORG in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Triage the top errors in production

    Show me the 5 most frequent unresolved errors from the `production` project in the last 24 hours, with: title, event count, first-seen, and stack-trace top frame. Propose a triage order.

    Tested with: Claude Desktop, Cursor.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Network
Sandbox
Read-only access to the Sentry API using the auth token passed in env. Scope is whatever the token was issued with.
Gotchas
  • Event payloads can contain customer PII — filter or scrub the output before piping it into other tools.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. security work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-security
Compare Sentry against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Sentry MCP vs [GitHub MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/sentry
- top-mcps.com listing for GitHub
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Sentry MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/sentry (fetch https://top-mcps.com/mcp/sentry.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (SENTRY_AUTH_TOKEN, SENTRY_ORG) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Security MCPs

Other tools in the same category worth evaluating.

Cloudflare
Official

Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.

cloudflareedgeworkersdns
10 minMedium

Exploring Top MCPs for Security? See all Security MCPs →