Provider · Database

Supabase — Ashlr Stack Provider

Supabase: Postgres + Auth + Storage. Full upstream provisioning via the Management API. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Database · OAuth (PKCE)

Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.

Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, use an available OAuth branch or a token fallback, 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 supabase

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

stack recommend "serverless postgres for a B2B SaaS"

Auth flow

Where configured, the adapter can use OAuth (PKCE); otherwise a credential-paste branch may be required. Review its current setup prerequisites.

How-to: Browser OAuth (PKCE) via the Ashlr Stack app.

Secret slots

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

SUPABASE_URL
SUPABASE_ANON_KEY
SUPABASE_SERVICE_ROLE_KEY

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

Supabase 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.

@supabase/mcp-server-supabase scoped to the new project ref, with SUPABASE_ACCESS_TOKEN piped from Phantom.

Starter templates that include Supabase

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

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

Neon — Serverless Postgres. Creates a project and pools the connection string.
Turso — Edge SQLite (libSQL). Creates a database in your default org.
Convex — Reactive backend-as-a-service. Deploy key stored in Phantom.
Upstash — Serverless Redis + Kafka. Management token stored in Phantom.
Firebase — Realtime DB + Auth. Service-account JSON stored verbatim in Phantom.

Catalog notes

v1 provisions a project and fetches service keys. Database password is auto-generated and stored in Phantom.

FAQ

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

Use an existing Supabase account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Where configured, the adapter can use OAuth (PKCE); otherwise a credential-paste branch may be required. Review its current setup prerequisites. OAuth does not establish automatic account signup; complete any required dashboard setup first.

Where does Stack store my Supabase credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY); 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 supabase` for local Supabase configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Supabase credentials through https://supabase.com/dashboard, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.