One command
Add Clerk 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 clerk
Or describe what you're building and let Claude pick it up via stack recommend:
stack recommend "drop-in user auth for my app"Auth flow
Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.
How-to: Paste a secret key from https://dashboard.clerk.com (API Keys).
Secret slots
stack add clerk writes these 1 secret
slot into your Phantom vault:
CLERK_SECRET_KEY
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.
Starter templates that include Clerk
Apply a pre-wired stack with one command:
-
stack init --template cloudflare-turso-clerk
Related providers in Auth
- Auth0 — Identity platform. Domain + M2M client credentials stored in Phantom.
- WorkOS — Enterprise SSO + Directory Sync. API key verified via GET /organizations.
FAQ
Do I need a Clerk account to use it with Stack?
Yes — Stack provisions Clerk on your behalf, but it authenticates as you. Paste a long-lived API key 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://dashboard.clerk.com and paste it once.
Where does Stack store my Clerk credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (CLERK_SECRET_KEY) 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 clerk` to pull the Clerk service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying Clerk credentials in their dashboard — https://dashboard.clerk.com — and Stack's next `doctor --fix` will pick up the new values.