Sentry

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: org:read, project:read, event:read, event:write.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
SENTRY_CLIENT_IDYesSentry OAuth Client ID from your public OAuth application Docs.
SENTRY_AUTH_TOKENNoSentry user auth token (org:read, project:read, event:read, event:write) that the local scaffold's client sends. The hosted connector uses OAuth instead. Docs.
SENTRY_ORGNoDefault Sentry organization slug for prompts that do not specify one Docs.

Setup

  1. Choose who owns the Sentry OAuth app: On hosted Veryfront, Sentry uses the Veryfront-managed Sentry OAuth app: connect Sentry from the project's integrations and approve the Sentry consent screen, no environment variables needed. Set SENTRY_CLIENT_ID only to use your own Sentry OAuth app, which is required for local and self-hosted runs.
  2. Create an OAuth application: In Sentry, open User settings, then API applications, and create a new application.
  3. Set the redirect URIs: Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/sentry for hosted Veryfront, or your app origin followed by /oauth/callback/sentry for a local or self-hosted app. Set SENTRY_CLIENT_ID from the app's credentials. The connector uses PKCE and sends no client secret.
  4. Verify access: Run List Organizations (read-only). It returns the organizations the connected user belongs to without changing anything.

Provider notes

  • The connection requests org:read, project:read, event:read and event:write. event:write is only needed by the tools that update issues.
  • Set SENTRY_ORG to default the organization slug the tools use.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Organizations<br /><code className="reference-identifier">sentry__list_organizations</code>ReadList organizations
List Projects<br /><code className="reference-identifier">sentry__list_projects</code>ReadList projects
List Issues<br /><code className="reference-identifier">sentry__list_issues</code>ReadList issues
Get Issue<br /><code className="reference-identifier">sentry__get_issue</code>ReadGet issue
Resolve Issue<br /><code className="reference-identifier">sentry__resolve_issue</code>WriteResolve issue
Get Latest Event<br /><code className="reference-identifier">sentry__get_latest_event</code>ReadGet latest event

Verify the connection

Call a read tool such as sentry__list_organizations with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.