Three paths to Stack
Pick the one that matches where you are. You can mix and match — most users start with the quickstart, then come back for the CLI reference.
Quickstart
Install, stack init, then
stack add supabase. Five minutes,
real output.
CLI reference
Every stack command with flags,
defaults, and real examples.
Providers
23 curated providers. What each one wires, which MCP it brings online, where its dashboard is.
What Stack is
Stack is a thin control plane over the services your app actually uses. It
drives the provider login, creates upstream resources (a Supabase project,
a Neon DB, a Sentry project), fetches their credentials, hands the secrets
to Phantom for encryption, and wires
.env.local, .mcp.json, and .stack.toml
in one shot.
# before: 45 minutes across 6 tabs
# after:
stack add supabaseWhat Stack isn't
- Not a secret manager. Every secret is stored by Phantom. Stack only knows the slot names.
- Not a deploy tool. We don't rebuild Vercel or Railway — we just give them the keys they need.
- Not a lock-in. Everything writes to standard files:
.env,.mcp.json,.stack.toml(TOML). Rip Stack out and your project still boots.
The whole map
Everything in these docs, grouped by purpose: