What scopes does the auth token need?

For read-only triage: `project:read`, `event:read`, `org:read`. Add `project:write` only if you want agents to assign issues or update status. Scoped auth tokens work — the broader "user auth token" is also supported but gives the agent more than it needs.

Can it read full stack traces?

Yes. The MCP returns each event's complete stack trace, breadcrumbs, request data, and tags. For minified frontend traces it can resolve source maps if your project has them uploaded to Sentry.

How does it handle issue fingerprinting?

The server returns Sentry's grouped issues — so agents see "this error has happened 23 times in the last hour" rather than 23 separate events. That signal is what makes auto-triage useful versus noisy.

Does it work with self-hosted Sentry?

Yes. Set the `SENTRY_HOST` environment variable to your self-hosted URL (e.g. `https://sentry.mycompany.com`) and the MCP routes API calls there instead of sentry.io.

Sentry

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

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

Score 78(?)SentryApache-2.0 650Verified May 28, 2026Top MCPs for Security →

Install View on GitHub

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

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "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.jsonshell

# 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.jsonjson

{
  "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.jsonjsonc

{
  "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.jsonjson

{
  "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.jsonjson

{
  "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.jsonjson

{
  "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.tomlshell

# ~/.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.jsonjsonc

{
  "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 (remote URL)json

{
  "name": "Sentry",
  "transport": "http",
  "url": "https://mcp.sentry.dev/mcp"
}

Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

2
Set required secrets
Set SENTRY_AUTH_TOKEN, SENTRY_ORG in your shell environment before launching your MCP client.
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.

May 28, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Apr 1, 2025
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

1Password

Official

Inject 1Password secrets into an AI agent's tool calls without exposing them in chat.

securitysecrets1passwordvault

8 minLow

HashiCorp Vault

Read dynamic and static secrets from HashiCorp Vault inside agent workflows.

securitysecretsvaulthashicorp

15 minMedium

Compared with Sentry

Side-by-side breakdowns for the choices people most often weigh against this MCP.

SentryvsGitHub SentryvsJam

Exploring Top MCPs for Security? See all Security MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

What scopes does the auth token need?

Can it read full stack traces?

How does it handle issue fingerprinting?

Does it work with self-hosted Sentry?

What changed

More Security MCPs

Cloudflare

1Password

HashiCorp Vault

Compared with Sentry