OrgMCP/ docs
Sign up
Documentation
Get started
Connectors
MCP integration
Reference
Enterprise
Misc

Sentry connector

The Sentry connector talks to your Sentry organisation with an Internal Integration or Personal Token and exposes six live MCP tools (projects, issues, latest event, releases, and sentry_diagnose). It is tools-only — there is no Index / Add button and no RAG crawler. Projects you can list in Sentry do not land in the knowledge index. Error data changes too quickly for a daily crawl.

Connect

  1. Do not use Settings → Developer Settings → Organization Tokens. Those are CI tokens with a fixed org:ci scope (source maps / sentry-cli) — they authenticate but 403 on projects and issues, and you cannot add scopes later.
  2. Create an Internal Integration (best for a company connector): Settings → Developer Settings → Custom Integrations → Create New Integration → Internal Integration. In the permissions dropdowns set at least Organization → Read (org:read — required to list the org and its projects), Project → Read, Issue & Event → Read, and Release → Admin (Sentry maps that to project:releases; there is often no Read). Then copy the generated token (sn_…).
  3. Or a Personal Token (bound to your user; dies if you leave the org): Settings → Developer Settings → Personal Tokens (or Account → API → Auth Tokens). Pick the same four scopes when creating it — they cannot be edited later.
  4. In the OrgMCP admin console, open Connectors → Add → Sentry.
  5. Paste the token (sn_… or a personal token) and the organisation slug (the path segment in https://acme.sentry.io — case-sensitive).
  6. Self-hosted Sentry: set Host to the origin only (e.g. https://sentry.example.com). Leave blank for Sentry SaaS — EU and US organisations live on a regional host (de.sentry.io, us.sentry.io). OrgMCP reads that from the sntrys_ token; do not set Host to sentry.io (org calls 403 for EU orgs). Identity GET /api/0/ still uses sentry.io — the regional host 404s that path.
  7. Click Test connection. Green means the token can see at least one project. A valid token with the wrong slug, or zero visible projects, fails.

What Test connection proves

Not just "the token authenticates". OrgMCP calls the Sentry user endpoint, then the organisation and a paginated project list. Zero projects is a red test — use sentry_diagnose (or the admin diagnostics panel) for host, slug, and the visible-project count.

MCP tools

  • sentry_list_projects / sentry_list_issues / sentry_list_releases — one page each; pass nextPageToken back as pageToken (Sentry cursor, not a page number).
  • sentry_get_issue / sentry_get_latest_event — latest-event 404 returns null. The event payload may include user email / ip from Sentry; do not dump breadcrumbs.
  • sentry_diagnose — auth mode, host, slug, visible project count + sample.

What does not get indexed

  • Nothing — this connector has no RAG ingest and no source_type. Use the live sentry_* tools (or another connector) for searchable knowledge.

Canonical matrix: docs/ARCH-connector-capabilities.md. Team+ plan (wave 2). See also GitLab for a similar diagnose + pagination bar.