Provider · Errors

Sentry — Ashlr Stack Provider

Sentry: Error + performance tracking. Attaches to an existing project and reads its DSN when available. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Errors · PAT

Sentry — Error + performance tracking. Attaches to an existing project and reads its DSN when available.

Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.

stack add sentry

Or retrieve catalog matches for what you're building via stack recommend:

stack recommend "error + performance tracking"

Auth flow

Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.

How-to: Paste an auth token from https://sentry.io/settings/account/api/auth-tokens/ (scopes: project:read, project:write).

Secret slots

stack add sentry has these 4 catalog secret slots; verify which values its adapter actually materializes through Phantom:

SENTRY_AUTH_TOKEN
SENTRY_DSN
SENTRY_ORG
SENTRY_PROJECT

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

MCP wiring

Sentry has an MCP entry in the catalog. An adapter may write a descriptor to .mcp.json. Inspect the actual file and complete supported client and credential setup; Claude Code / Cursor / Windsurf availability is not established by the descriptor. Shell expressions in JSON remain literal.

@sentry/mcp-server with SENTRY_AUTH_TOKEN piped from Phantom and SENTRY_HOST defaulting to sentry.io.

Starter templates that include Sentry

Selected template init attempts provider setup by default; add --noProvision to inspect config first:

stack init --template nextjs-neon-vercel-sentry
stack init --template supabase-posthog-sentry-resend

FAQ

Do I need a Sentry account to use it with Stack?

Use an existing Sentry account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://sentry.io and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Sentry credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (SENTRY_AUTH_TOKEN, SENTRY_DSN, SENTRY_ORG, SENTRY_PROJECT); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove sentry` for local Sentry configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Sentry credentials through https://sentry.io, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.