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 posthog
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "product analytics and feature flags"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 personal API key at https://app.posthog.com/me/settings (scope: all).
Secret slots
stack add posthog has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
POSTHOG_PERSONAL_API_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
PostHog 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.
SSE MCP at mcp.posthog.com/sse, with the personal key piped through Phantom at call time.
Starter templates that include PostHog
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
Related providers in Analytics
- Mixpanel — Product analytics. Project token + optional API secret stored in Phantom.
- Plausible — Privacy-friendly web analytics. API key verified against the stats API.
FAQ
Do I need a PostHog account to use it with Stack?
Use an existing PostHog 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.posthog.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my PostHog credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (POSTHOG_PERSONAL_API_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 posthog` for local PostHog configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying PostHog credentials through https://app.posthog.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.