Provision Resource
provision_resourceProvision a Floot-managed backend resource for the project, fully server-side (Floot mints the secrets), and seed the working code for it. Idempotent: re-running returns the existing resource and skips seed files that exist. Available:
database — A Floot-managed Postgres database (Neon). FLOOT_DATABASE_URL is set for the app.
auth — Email/password + session auth (JWT_SECRET, auto-provisions a database if none). Injects auth pages, endpoints, and helpers.
oauth-login — Sign in with Google via Floot's brokered OAuth (FLOOT_OAUTH). Injects OAuth provider classes, login buttons, helpers.
microsoft-login — Sign in with Microsoft via Floot's brokered login (FLOOT_MICROSOFT_LOGIN). Injects button + auth endpoints.
google-integration — Built-in Google integration (FLOOT_GOOGLE_INTEGRATIONS): end users connect their Google account so the app reads/writes their Gmail, Calendar or Drive, unless the user wants their own Google client. See get_guides("floot-provided-google-integrations").
microsoft-integration — Microsoft Graph access (Outlook/Teams/etc.) via Floot's brokered Microsoft OAuth (FLOOT_MICROSOFT_INTEGRATIONS). Injects Connect button + endpoints.
push-notifications — Web + native push (FLOOT_PUSH). Mints VAPID keys, injects helpers/pushClient (subscribe/unsubscribe) + a service worker.
self-edit — Lets the app edit ITS OWN source through the Floot MCP server (FLOOT_SELF_EDIT): mints a project-scoped bearer token, exposed to the backend as FLOOT_PROJECT_TOKEN + FLOOT_PROJECT_ID. Duplicates get their own token. No seed code — see get_guides("floot-self-edit").
payments — Built-in payments (FLOOT_PAYMENTS), unless the user wants their own Stripe account. See get_guides("floot-payments").
shipping — Shipping physical goods through the owner's own Shippo account (FLOOT_SHIPPING: rates, labels, tracking); the preview uses built-in test shipping. See get_guides("floot-shipping"). Other enum values are beta-gated. Sending email needs no resource (@floot/email, get_guides("email")). The user's OWN key (their OpenAI key, an external database) goes through request_external_resource. Turning Floot Payments OFF (publishing is refused while it is attached with Stripe setup unfinished, also when the app no longer uses it): action "turn_off" with resource "payments". Owner only; ask the user first. It keeps the app's data and Stripe setup; the owner turns it back on in Floot (Services → Payments). Turning Floot Shipping OFF (publishing is refused while it is attached and Shippo is not connected, also when the app ships nothing): action "turn_off" with resource "shipping". Edit access; ask the user first. It keeps the app's data and Shippo connection; provisioning "shipping" again turns it back on.
app-connection — let this project's backend call functions ANOTHER Floot app exports (no API keys): pass app_target and app_functions. Only apps the user can edit, only functions in the other app's helpers/flootAppExports.tsx (saved is enough: write both apps first, connect, then publish both); the user confirms in a dialog. Read get_guides("app-calls") first.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"resource": "<resource>"
},
"name": "provision_resource"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | No | Default "provision". "turn_off" only with resource "payments" (turns Floot Payments off, owner only) or "shipping" (turns Floot Shipping off, edit access); only after the user confirms. | |
| app_note | No | Only for resource "app-connection": one sentence for the user on why this project needs these functions. Shown in the confirmation dialog. | |
| resource | Yes | ||
| projectId | Yes | ||
| app_target | No | Only for resource "app-connection": the OTHER Floot app — its project id, name.floot.app address or custom domain. | |
| app_functions | No | Only for resource "app-connection": the exact function names this project needs from the other app's helpers/flootAppExports.tsx. |