Provider · Errors

Sentry — Ashlr Stack Provider

Sentry: Error + performance tracking. Creates a project and fetches its DSN. Wire it into your project with one command via Ashlr Stack.

Errors · PAT

Sentry — Error + performance tracking. Creates a project and fetches its DSN.

Dashboard ↗

One command

Add Sentry to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.

stack add sentry

Or describe what you're building and let Claude pick it up via stack recommend:

stack recommend "error + performance tracking"

Auth flow

Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom.

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 writes these 4 secret slots into your Phantom vault:

SENTRY_AUTH_TOKEN
SENTRY_DSN
SENTRY_ORG
SENTRY_PROJECT

The values never leave Phantom in plaintext. Your .env file references slot names, and stack exec -- <cmd> swaps them in at process-spawn time via Phantom's local proxy.

MCP wiring

Sentry ships an MCP server. stack add sentry auto-wires it into .mcp.json so your Claude Code / Cursor / Windsurf session can use it immediately.

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

Starter templates that include Sentry

Apply a pre-wired stack with one command:

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?

Yes — Stack provisions Sentry on your behalf, but it authenticates as you. Paste a personal access token (PAT) once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://sentry.io and paste it once.

Where does Stack store my Sentry credentials?

In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (SENTRY_AUTH_TOKEN, SENTRY_DSN, SENTRY_ORG, SENTRY_PROJECT) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.

Can I rotate or revoke this integration later?

Yes. Run `stack remove sentry` to pull the Sentry service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Sentry credentials in their dashboard — https://sentry.io — and Stack's next `doctor --fix` will pick up the new values.