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 stripe
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "accept payments from customers"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: Create a restricted key at https://dashboard.stripe.com/apikeys (use test mode for development).
Secret slots
stack add stripe has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
STRIPE_SECRET_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
Stripe 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.
@stripe/mcp with STRIPE_SECRET_KEY piped from Phantom — create products, prices, and inspect events from the agent.
Catalog notes
v1 only stores the key. Full Stripe Connect / account linking lands when we register the Ashlr OAuth app.
FAQ
Do I need a Stripe account to use it with Stack?
Use an existing Stripe 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://dashboard.stripe.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Stripe credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (STRIPE_SECRET_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 stripe` for local Stripe configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Stripe credentials through https://dashboard.stripe.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.