{"id":"com.floot/floot","slug":"com-floot-floot","title":"Floot","description":"Build and publish full-stack web and mobile apps on Floot from any MCP client. Building is free.","version":"1.0.0","publisher":{"kind":"domain","id":"floot.com","label":"floot.com","url":"https://floot.com"},"website":"https://floot.com","repository":"","remotes":[{"type":"streamable-http","url":"https://mcp.floot.com/mcp"}],"packages":[],"published":"2026-07-15","updated":"2026-07-15","status":"online","auth":"","latency_ms":946,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search","title":"Search Projects","description":"Search your Floot projects and their code. Returns result ids usable with fetch. For richer options, list_projects enumerates projects and search_code does code-level search.","read_only":true},{"name":"fetch","title":"Fetch Search Result","description":"Fetch a search result by id: a project overview ('<projectId>') or a file ('<projectId>:<path>'). For direct access to a known file or project, read_file/list_files give more detail.","read_only":true},{"name":"list_projects","title":"List Projects","description":"List your Floot projects (id, name, last-updated, whether an app icon is set), most recently updated first. name_filter is a case-insensitive substring match on the stored name, which is often not the name the user uses for a project — on a small account a filter that matches nothing returns the whole list instead.","read_only":true},{"name":"list_resources","title":"List Available Resources","description":"List the env vars a project's code can use and the resources behind them: (1) resources CONNECTED to the project — usable as process.env.<NAME> in endpoint code now; (2) the owner's other account-level credentials — reusable, but not usable in code until connected; (3) everything Floot can add. Call it to learn what env vars exist before writing backend code, and BEFORE provisioning or requesting ","read_only":true},{"name":"list_files","title":"List Project Files","description":"List a Floot project's virtual file tree with sizes, plus its dependencies, current version (pass the version to write tools as expected_version), and current project metadata — title, description, app icon (iconUrl), splash screen, mobile app id, SSR, iOS Info.plist overrides, share target (iOS + Android), native system bars. This is where to look up those settings; update_project_metadata change","read_only":true},{"name":"read_file","title":"Read File","description":"Read a file from a Floot project (cat -n style); offset/limit for large files, column to start mid-line (a capped read names the offset and column to continue from). Paths: components/Name.tsx, components/Name.module.css, helpers/Name.tsx, pages/name.tsx, pages/name.pageLayout.tsx, endpoints/route_POST.ts, endpoints/route_POST.schema.ts, static/file.txt, base.css. include_references:true also list","read_only":true},{"name":"read_files","title":"Read Files","description":"Read up to 20 files in ONE call, much cheaper than repeated read_file: prefer it whenever you need several files together (an endpoint, its .schema.ts and the hook that calls it). Same paths and options as read_file (diagnostics, include_references; /_cdn/<name> images come back as images), each file cat -n style under a header. Output is capped: whole files at the end are left out and listed by n","read_only":true},{"name":"search_code","title":"Search Code","description":"Search a Floot project's files (string or regex) with optional glob filters (e.g. ['components/*', 'endpoints/**']). Returns file:line excerpts plus filename matches; capped at 40 results.","read_only":true},{"name":"get_guides","title":"Floot Guides","description":"Floot documentation for agents. Call with no arguments to list available guides. Pass `topic` for one guide (e.g. topic:'floot-overview') or `topics` (an array of ids) to fetch several at once. floot-overview explains how Floot projects work — read it before your first code change. Skill guides that ship seed code (marked in the list) AUTO-INJECT it into the project the first time they're loaded w","read_only":false},{"name":"write_file","title":"Write File","description":"Create or fully overwrite a file in a Floot project. Content is written literally. Paths must follow the item scheme (see read_file); invalid paths are rejected with the rule they broke. Pass expected_version (from list_files/read_file) to detect concurrent edits. Writing components/Name.module.css sets the css of components/Name — other properties of the item are preserved.","read_only":false},{"name":"edit_file","title":"Edit File","description":"Replace old_string with new_string in a project file. old_string must match the current content exactly (including whitespace) and be unique unless replace_all is set. Prefer this over write_file for changes to existing files.","read_only":false},{"name":"delete_file","title":"Delete File","description":"Delete a project file. Deleting an item's main code file (e.g. components/Foo.tsx) removes the whole item including its css/tests; deleting an aux file (e.g. Foo.module.css) only clears that part.","read_only":false},{"name":"remove_dependency","title":"Remove Dependency","description":"Remove npm packages from a Floot project's dependency record (record-only; nothing runs).","read_only":false},{"name":"create_project","title":"Create Project","description":"Create a new Floot project (pre-seeded with the shared component library) and return its id. `initial_prompt` describes the app to build — what it does and for whom — keeping the user's own wording where they gave one rather than a summary. It becomes the project's system prompt (static/__dev/system-prompt.md, which the user can edit) and grounds the project (served back as <project-instructions> ","read_only":false},{"name":"apply_patch","title":"Apply Patch","description":"Apply a V4A patch to a Floot project — create and update multiple files in ONE atomic operation. Format: \"*** Begin Patch\" envelope with \"*** Add File: path\" (+ prefixed lines) and \"*** Update File: path\" (hunks: optional \"@@ anchor\" locator, space-prefixed context, -/+ lines, optional \"*** End of File\"), then \"*** End Patch\". Paths follow the Floot item scheme (see read_file). To replace a file w","read_only":false},{"name":"get_logs","title":"Get Logs","description":"Call FIRST when debugging a runtime problem (a 500, a failed request, a blank page, 'it doesn't work'), before theorizing. Sources:\n- 'server' (default): the dev backend's request logs, last hour (method, URL, status, duration, log lines), background jobs included; log_reference_id: one request in full.\n- 'browser': console output and client network requests (`⇄ METHOD url → status`, error body of","read_only":true},{"name":"typecheck","title":"Typecheck Project","description":"Typecheck the project (incremental tsc on the project VM). Type errors don't block the app from running. Without paths it checks only code that ships: spec (*.spec.tsx), example (*.example.tsx) and design (designs/) files are skipped, and the result says how many. Pass paths to check named files, those included, plus their direct importers. run_tests runs specs.","read_only":true},{"name":"run_tests","title":"Run Tests","description":"Run the project's Jasmine specs (helpers/*.spec.tsx) on the project VM (jsdom): specs may render components (@testing-library/react) or call endpoint handlers and backend helpers directly. Limits: fetch throws inside tests (mock with spyOn(globalThis, \"fetch\")), process.env secrets are absent (give a module that reads one at load a dummy value from a helper the spec imports BEFORE it, e.g. helpers","read_only":true},{"name":"add_dependency","title":"Add Dependency","description":"Add npm packages to the project (validated against Floot's supported set — rejected packages get a supported alternative named; some versions are pinned/substituted). Avoid node-gyp/native packages (exception: sharp is supported, auto-pinned), WASM modules, and packages bundling large binaries (e.g. ffmpeg/ffprobe); pure JS/TS preferred. A bare `kysely` keeps the version the project already record","read_only":false},{"name":"run_code_in_vm","title":"Run Code in VM","description":"Run a Node.js snippet on the project's compute VM and return its stdout and stderr. ESM by default (a bare require() snippet runs as CJS). The project's npm dependencies are importable and the network works, so a snippet can call the project's /_api/* endpoints (get_preview_url → apiBaseUrl). The project's env vars, secrets and source files are not available.\n\nFor data too large to pass through th","read_only":false},{"name":"run_code_in_browser","title":"Run Code in Browser","description":"Run a TypeScript snippet inside the running app's preview document in the user's open Floot editor and return the string it returns. `document` and `window` are the app's own DOM: measure elements, read computed styles and rendered output, or click a button and read the result. Runs at the project root, so project files import by relative path, and browser APIs (canvas, createImageBitmap, WebGL) w","read_only":false},{"name":"delete_storage_file","title":"Delete Storage Files","description":"Delete files from the project's storage (what the app uploaded or serves from /_cdn/), by their full keys as run_code_in_vm's _floot.storageList returns them (\"public/…\" or \"private/…\"), up to 100 per call. The bytes are gone for good. For a public file of a published app, its CDN copy is removed too; the result says what to tell the user about that. Only when the user asked for the files to be de","read_only":false},{"name":"call_app_function","title":"Call App Function","description":"Call one function of this project's own backend, the way its own code would: a function the project exports from helpers/flootAppExports.tsx, run in its published app, returning that function's JSON result. list_files shows the project's exported functions with their signatures; the function name and its input come from there. Use it to test an export after publishing it, or to do something for th","read_only":false},{"name":"navigate_preview","title":"Navigate the User's Preview","description":"Point the user's OPEN Floot preview at what you built, to SHOW it to them; pair it with screenshot_preview to see it yourself. targetType \"page\": the app's router goes to `path`. \"component\": the component's .example.tsx for `name` (if it has none, say so or create one). \"page-examples\": the staged screens in pages/<name>.__example.tsx (the file must exist), listing them; \"#<screen>\" opens one. \"d","read_only":true},{"name":"screenshot_preview","title":"Screenshot the User's Preview","description":"Capture a screenshot of the user app. Call it whenever you want to SEE what the app currently looks like (layout, styling, rendered state) or want to debug the app. By default it shows whatever device the user has the preview on. Pass `viewport` to see it on another device — this is how to check a mobile or tablet layout: the preview switches to that device for the capture only, then back. Never b","read_only":true},{"name":"get_current_context","title":"Get Current Editor Context","description":"What the user is looking at RIGHT NOW in their open Floot editor: the active page/component, the preview element they selected (mapped to source file:line), the preview device size, whether they drew a screenshot annotation for you, whether they REVERTED recent changes (undoing edits — re-read before editing if so), and any requests they queued via editor action buttons (\"Fix with Floot\" etc.). Ca","read_only":true},{"name":"view_annotation","title":"View Annotation","description":"View a screenshot annotation the user drew on the app preview (annotationId comes from get_current_context). Returns the annotated image — the user's drawings/text point at what they mean. Annotations expire after ~1 day.","read_only":true},{"name":"get_job_status","title":"Get Job Status","description":"Poll a pending tool call by its jobId. Each poll either returns the final result (succeeded/failed/cancelled), or reports the call as still running — call it again until you get the result. Failed calls return their stored error message. A jobId belongs to exactly ONE task: it never blocks other tools or other jobs (run them freely in parallel), and once terminal it is frozen history — a NEW user ","read_only":true},{"name":"rename_file","title":"Rename File","description":"Rename one or more items and automatically rewrite every file that imports them. Use item names WITHOUT extensions (e.g. {from:'components/OldName', to:'components/NewName'}). Preferred over delete+create — preserves content and fixes importers. Same type only. Pass several renames to apply them atomically in ONE pass; importer rewrites are resolved across the whole batch (including chains where o","read_only":false},{"name":"copy_file","title":"Copy File","description":"Copy one or more items to new names (e.g. {from:'components/Card', to:'components/BigCard'}). Item names without extensions; same type only. Importers of the source are left unchanged. Pass several copies to apply them in one call.","read_only":false},{"name":"query_database","title":"Query Database (Read-Only)","description":"Run a READ-ONLY SQL query against the project's Postgres database (SELECT, EXPLAIN, etc.) — the Floot-managed database, or an external Postgres the user connected to the project. Writes are rejected — use execute_sql for those. Returns JSON: `{rows, rowCount, command, truncated?}` (or `{results: [...]}` for multi-statement queries). Pass `database` only if the project has more than one.","read_only":true},{"name":"get_live_payments","title":"Get Live Payments (Read-Only)","description":"Look up your Floot Payments records in Stripe across all your projects: one record by id, or a list of one record type. Read-only. Reads LIVE mode unless mode is \"test\", which reads the test payments made in the preview (those never appear in the user's Stripe dashboard). Refunds, cancels and every other change are not possible here; for those the user logs in at stripe.com. Read get_guides('live-","read_only":true},{"name":"get_analytics","title":"Get Visitor Analytics","description":"The published app's visitor analytics, as the editor's Analytics tab shows them: visitors, page views and a daily trend, top pages, referrers, countries, devices, browsers and custom events (trackEvent) over a date range. Read-only. Tracking setup and consent: get_guides('analytics').","read_only":true},{"name":"execute_sql","title":"Execute SQL (Writes)","description":"Run WRITE SQL on the project's Postgres database (Floot-managed or an external one the user connected): CREATE/ALTER, INSERT, UPDATE, DELETE, DROP, migrations. Your MCP client shows the user the SQL to approve. Schema changes re-pull the typed schema helper and return the new schema. Pass `database` only if the project has more than one. By default the whole query (every statement in it) runs on o","read_only":false},{"name":"pull_database_schema","title":"Pull Database Schema","description":"Introspect the database and write a typed schema helper the app uses for queries (kysely on current projects; some legacy projects use drizzle or snake_case kysely — the pull matches whatever the project already uses). Usually NOT needed after execute_sql — schema-changing statements re-pull automatically. Use it to refresh manually, or with helper_name to generate the helper for an additional/ext","read_only":false},{"name":"create_checkpoint","title":"Create Checkpoint","description":"Create a NAMED checkpoint — a labeled restore point the user sees in the project's Checkpoints panel and can revert to later. All file/dependency changes since the previous checkpoint are grouped under it. Call this AFTER completing a coherent unit of work (a feature, a fix, a requested change set) — not after every file write. Give it a short user-meaningful title describing what was accomplished","read_only":false},{"name":"update_project_metadata","title":"Update Project Metadata","description":"Update project settings; current values appear at the top of list_files. Changes reach the published app at the next publish. Settings marked \"on request\" change only when the user asks about that subject.\n- updates (flat keys): title (2-100 chars), description, iconUrl (app icon: favicon, home-screen and native icon; a /_cdn/static/… path from upload_asset, generate_image or request_user_upload, ","read_only":false},{"name":"generate_image","title":"Generate Image","description":"Generate AI images into the project's asset storage, for PROJECT-SPECIFIC imagery (mascots, illustrations, app icons, a particular style); generate them BEFORE building the components that use them. Returns project-relative paths (/_cdn/static/...) that resolve on the app's own domain: use them in code, or as the app icon via update_project_metadata iconUrl. An image you already hold as a file goe","read_only":false},{"name":"upload_asset","title":"Upload Asset","description":"Upload a binary asset (image, font, audio, …) you actually hold (generated, downloaded or read yourself) to the project's storage. The user's chat attachments never reach MCP servers (you see attached images by vision only): use request_user_upload, where the user picks the file again. For fresh AI images use generate_image.\n- ChatGPT conversation files (a generated image, a file ChatGPT holds): p","read_only":false},{"name":"request_user_upload","title":"Request a File From the User","description":"Show the user an inline upload card so they can hand you a file from their device (image/font/audio/…) — it lands in the project's hosted assets and the card gives you the hosted publicUrl. This is the path for any file the user has: an image they attached in this chat (attachments never reach MCP servers — you see them through vision only, so the user re-picks the same file here), a file on their","read_only":false},{"name":"card_upload_asset","title":"Upload Card Bridge","description":"Internal bridge for the upload card (not for agents — use request_user_upload / upload_asset). phase 'presign' mints the PUT URL for the picked file; phase 'complete' verifies the object landed and finishes the request_user_upload call with the publicUrl.","read_only":false},{"name":"provision_resource","title":"Provision Resource","description":"Provision 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:\n- database — A Floot-managed Postgres database (Neon). FLOOT_DATABASE_URL is set for the app.\n- auth — Email/password + session auth (JWT_SECRET, auto-provisions a ","read_only":false},{"name":"request_external_resource","title":"Request External Resource","description":"Request the user's own credential for an outside service on this project: their OpenAI or Anthropic key, an external Postgres database (type POSTGRES), or any other service's key (type GENERIC, with secret_env_vars). Floot-managed resources (database, auth, push, …) need no user input: use provision_resource. Request it early and keep building; code can reference process.env.<NAME> before the user","read_only":false},{"name":"get_publish_status","title":"Get Publish Status","description":"Read-only publish snapshot for a project: published (true/false, with the live URL when published), customDomains (the user's own domains attached to the project — apex and www are listed separately; empty when none), paid (the workspace owner has a paid plan, which allows removing the Floot badge), plan (free | pro | power — `paid` cannot tell Pro from Power), nativeBuilds (the owner's remaining ","read_only":true},{"name":"compare_published_source","title":"Compare With Published Source","description":"Read-only: the source changes a publish now would ship. Current saved code vs the live release (or release): both source digests (equal = identical) and every changed file with both sha256s, paged by offset; diffs only for the paths given. Paid plans.","read_only":true},{"name":"publish_app","title":"Publish App","description":"Publish the app to production: the first publish, a new publish of changes the user wants live, or a custom domain. Read get_guides('publishing') before your first call. A live app publishes at once, nothing to pass or confirm. A first publish (no domain) shows the user the publish form, and nothing publishes until they press Publish. Always publishes live (web, the mobile app when built, payments","read_only":false},{"name":"unpublish_app","title":"Unpublish App","description":"Take the published app offline and release its subdomain — destructive, confirm with the user first. Details: get_guides('publishing').","read_only":false},{"name":"cancel_request","title":"Cancel Request","description":"Withdraw a pending request you created — a credential request from request_external_resource, a custom-domain setup request from publish_app, or an open screenshot job from screenshot_preview (jobId from that tool). Only pending requests can be cancelled — completed ones are final — and cancelling is final too: a cancelled request can't be resumed (the user would need a new one). Use when the user","read_only":false},{"name":"get_preview_url","title":"Get Preview URL","description":"Show the user a live preview card and return the preview link. On an EXISTING project this is typically called EARLY, before the first change, so the user watches edits live from the start; the result is informational and a working session normally continues past it. It is not needed right after create_project, whose result already includes the same card. The preview URL carries an access token in","read_only":true}],"server_info":{"name":"floot","version":"1.0.0"},"category":"productivity","tags":["news","data","developer"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":219204,"score":100,"indexable":true,"first_seen":"2026-07-15","stars":0,"badges":["official"],"sponsor":null,"page":"https://agentsindex.org/agents/com-floot-floot/"}