Tool Integration
Connect required services manually or through an available MCP connector, and record evidence without exposing secrets.
Tool integration
Use this page after initialization has generated docs/KEYS.md. The AI Pro and Standard development branches contain integrations for Wire, Supabase, Firebase, Google sign-in, RevenueCat, and EAS. The initializer plans setup, but it does not create accounts, modify provider consoles, or verify a connection.
Choose a mode, then prove the result
Each required service accepts mcp, manual, or later. An optional service may also use skip. Wire cannot be skipped because its activation, lifecycle, experiment, and learning plan is part of every initialized product.
| Mode | What it means | Initial status |
|---|---|---|
mcp | Ask the active coding host to use a connector it actually exposes | manual_required until the host completes the action and returns evidence |
manual | Follow the provider guide and configure the account yourself | manual_required |
later | Keep the work explicitly deferred | pending |
skip | Exclude an optional service from the selected scope | skipped |
mcpAvailable: true is a capability hint, not a connection receipt. The Node initializer never reports a service as connected merely because the mode says mcp.
Required evidence
Keep secret values out of answers.json, generated Markdown, terminal transcripts, and git. docs/KEYS.md records variable names, setup mode, status, source instructions, and evidence only.
A service moves to connected or verified only after a real check against the buyer's account. Examples include a successful authenticated provider read, a lifecycle event visible in the buyer workspace, or a native purchase configuration read from the buyer's RevenueCat project. A green build proves none of those things. Charming, but useless as an account receipt.
Recommended order
- Wire: define the activation event and lifecycle map, then connect the workspace manually or through an exposed connector. See Wire onboarding and growth.
- Supabase: configure the buyer's database and authentication project. See Supabase Setup.
- Firebase and Google sign-in: register the exact iOS bundle identifier and Android package before downloading config files. See Firebase Setup.
- RevenueCat: configure products and entitlements when monetization is in scope. See RevenueCat Setup.
- EAS: connect the buyer's Expo project and platform credentials after identity cleanup. See Expo Dev Setup.
Wire owns ordinary product analytics after activation. Firebase remains a separate native-services integration for Crashlytics, messaging, and explicit Firebase operations. Do not configure Firebase Analytics as an ordinary-event fallback.
Manual path
Follow each linked provider guide, add local environment values through .env, and update the status and evidence in the initialization state without copying the secret itself into a document. Run the provider-specific check before marking the service verified.
MCP path
First ask the active host to enumerate its available tools. If the requested connector is absent, keep the status manual_required and use the manual guide. If it is present, review the requested action, run the smallest scoped operation, and retain a non-secret receipt.
The repository entry files for Codex, Claude Code, and Gemini CLI expose the same workflow contract. Their presence does not prove that those hosts, their subagents, or an MCP connector ran on this machine.
Pending is a valid planning result
An initialized_with_pending tree is safe for document review and bounded source work after explicit acceptance. It is not ready for native launch or release. Complete the required account, credential, asset, and provider checks before running release preflight.
Next
When all native prerequisites are present, continue to First App Launch. Release preflight remains the only initializer gate that may grant release_ready, and a real native build is still separate evidence.
For the current two-person round, test AI Pro merge commit a7f6cb36f1fc3ecd8b3a7d9c8956afa30bf39984 from PR #30. Report the commit, platform, source-gate result, native result, Wire event receipt, and static-fallback result without including secrets.