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 firebase
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "serverless postgres for a B2B SaaS"Auth flow
Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.
How-to: Paste the full service-account JSON from Firebase → Project settings → Service accounts.
Secret slots
stack add firebase has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
FIREBASE_SERVICE_ACCOUNT_JSON
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.
Related providers in Database
- Supabase — Postgres + Auth + Storage. Full upstream provisioning via the Management API.
- 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.
FAQ
Do I need a Firebase account to use it with Stack?
Use an existing Firebase account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://console.firebase.google.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Firebase credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (FIREBASE_SERVICE_ACCOUNT_JSON); 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 firebase` for local Firebase configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Firebase credentials through https://console.firebase.google.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.