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 launchdarkly
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "I need a featureflags provider"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: Find your SDK key in LaunchDarkly → Environments and create an API token at LaunchDarkly → Account settings → Authorization.
Secret slots
stack add launchdarkly has these 2 catalog secret
slots; verify which values its adapter actually materializes through Phantom:
LAUNCHDARKLY_SDK_KEYLAUNCHDARKLY_API_TOKEN
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.
FAQ
Do I need a LaunchDarkly account to use it with Stack?
Use an existing LaunchDarkly 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://app.launchdarkly.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my LaunchDarkly credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (LAUNCHDARKLY_SDK_KEY, LAUNCHDARKLY_API_TOKEN); 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 launchdarkly` for local LaunchDarkly configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying LaunchDarkly credentials through https://app.launchdarkly.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.