One command
Run one provider setup from an initialized project. Its adapter may handle auth inputs, use an available OAuth branch or a token fallback, 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 github
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "git hosting and CI"Auth flow
The catalog describes an OAuth device flow. Actual adapter setup may use a token fallback; check the installed interface and provider permissions.
How-to: Browser device-code flow — enter the code GitHub shows you, authorise, done.
Secret slots
stack add github has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
GITHUB_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.
MCP wiring
GitHub 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.
@modelcontextprotocol/server-github with GITHUB_PERSONAL_ACCESS_TOKEN piped from Phantom.
FAQ
Do I need a GitHub account to use it with Stack?
Use an existing GitHub account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. The catalog describes an OAuth device flow. Actual adapter setup may use a token fallback; check the installed interface and provider permissions. OAuth does not establish automatic account signup; complete any required dashboard setup first.
Where does Stack store my GitHub credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (GITHUB_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 github` for local GitHub configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying GitHub credentials through https://github.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.