Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.floot/floot

REMOTE · MCP.FLOOT.COM

Build and publish full-stack web and mobile apps on Floot from any MCP client. Building is free.

Available components

−1 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability45
  • 18% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 13720 tokens (~190/item across 72 items; 58 tools + 14 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 27% of tool parameters carry a description.Partial
Tool Safety94
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 9 of 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "read_merge_conflict" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 −1
    • New tool “card_confirm_merge”, which the server declares destructive security
    • New tool “delete_branch”, which the server declares destructive security
    • New tool “start_merge”, which the server declares destructive security
    • Tool “navigate_preview” rewrote its description, which is the text the model reads security
    • Tool “run_code_in_vm” rewrote its description, which is the text the model reads security
    • Destructive annotations: 86% → 75% ▼ functional
    • Schema quality: 12199 → 13720 ▼ functional
    • New tool “compare_branches” functional
    • New tool “fork_project” functional
    • New tool “get_branch_settings” functional
    • New tool “get_merge_status” functional
    • New tool “list_branches” functional
    • New tool “read_merge_conflict” functional
  • 19 Nov 26 0
    • Tool “read_file” rewrote its description, which is the text the model reads security
    • Tool “typecheck” rewrote its description, which is the text the model reads security
    • New tool “compare_published_source” functional
    • “read_file” added an optional parameter “column” cosmetic
  • 18 Nov 26 0
    • Tool “get_preview_url” rewrote its description, which is the text the model reads security
    • “get_preview_url” added an optional parameter “name” cosmetic
    • “get_preview_url” added an optional parameter “path” cosmetic
    • “get_preview_url” added an optional parameter “targetType” cosmetic
  • 17 Nov 26 0
    • Tool “call_app_function” rewrote its description, which is the text the model reads security
    • Tool “get_logs” rewrote its description, which is the text the model reads security
    • Tool “get_publish_status” rewrote its description, which is the text the model reads security
    • “call_app_function” added an optional parameter “scheduled_job” cosmetic
    • “call_app_function” made “function” optional cosmetic
  • 16 Nov 26 0
    • Stability: fail → pass ▲ security
  • 15 Nov 26 0
    • Tool “update_project_metadata” rewrote its description, which is the text the model reads security
    • New tool “get_analytics” functional
  • 12 Nov 26 0
    • Tool “run_code_in_browser” rewrote its description, which is the text the model reads security
  • 11 Nov 26 0
    • Tool “publish_app” rewrote its description, which is the text the model reads security
    • New resource “floot-merge-card” functional
    • New resource “floot-merge-card-gpt” functional
    • “publish_app” reworded the description of “domain” cosmetic
    • “publish_app” reworded the description of “domain_type” cosmetic
    • “request_external_resource” reworded the description of “name” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.floot.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=floot.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 1 Jul 2026 14 Jan 2027 RSA 2048 SHA256-RSA 902d2fdfbf107a3d1db1dc0c72ee93a
SANs: floot.com, combini.ai, *.combini.ai, combini.dev, *.floot.com, *.combini.dev
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.floot.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
floot.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.floot.com/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.floot.com/.well-known/oauth-protected-resource"
Header Value
www-authenticate Bearer resource_metadata="https://mcp.floot.com/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://mcp.floot.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.floot.com/mcp
Authorisation server https://mcp.floot.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.floot.com/mcp Verified 200
http (plaintext) http://mcp.floot.com/mcp HTTPS enforced 301 https://mcp.floot.com/mcp
MCP tools · 58 exposed · ~13,138 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_dependency ~188

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 records (a project without one gets 0.28.17), the version its db/schema helpers are written against; pass an explicit `kysely@<version>` only when upgrading it deliberately. Installs on the project VM and persists resolved versions. After a slow install completes as a job, call add_dependency again with the same packages — the second call is fast and persists.

NameTypeReqDescription
packagesarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

apply_patch ~258

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 wholesale use Add File on its own path; the item's other files (e.g. its .module.css) are kept. This tool does not delete or rename: "*** Delete File:" sections are skipped and listed in the result (delete_file removes files), and "*** Move to:" is rejected (rename_file renames items and rewrites their importers). Every applied patch is recorded in the project history and can be reverted. Keep each patch MODEST (a few files / few hundred lines): chat clients cap per-message output, and a patch cut off mid-way is rejected whole ("missing *** End Patch") — split big changes across several apply_patch calls.

NameTypeReqDescription
expected_versioninteger––
patchstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

call_app_function ~307

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 the user through the app's own logic instead of raw SQL. The function runs for real (a function that writes, sends or charges does so), so call one that changes anything only when the user asked for that change. Only functions in the last publish; needs edit access to the project. Up to 25 seconds; no answer in time does not mean it did not run. Details: get_guides("app-calls"). - scheduled_job (of static/__dev/scheduled-jobs.json) instead: runs it once now on the preview backend, like the editor's Run now; no publish or branch switch needed.

NameTypeReqDescription
functionstring–The name of a function this project exports from helpers/flootAppExports.tsx, as list_files shows it.
input––The function's argument as JSON, of the type its signature in list_files shows. Omit for a function that takes none.
projectIdstringyes–
scheduled_jobstring––
timeout_secondsinteger–How long to wait for the function, in seconds.

No output schema declared.

No examples provided.

cancel_request ~110

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 says to stop or they don't want to proceed.

NameTypeReqDescription
jobIdstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

card_confirm_merge ~38

Internal bridge for the merge card's Merge button (not for agents).

NameTypeReqDescription
jobIdstringyes–
secretstringyes–

No output schema declared.

No examples provided.

card_upload_asset ~110

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.

NameTypeReqDescription
content_typestring––
file_namestring––
jobIdstringyes–
phasestringyes–
projectIdstringyes–
size_bytesinteger––

No output schema declared.

No examples provided.

compare_branches ~245

Show what merging one branch into another branch of the same project would change. projectId is always the TARGET (the branch merged into); sourceProjectId is the branch merged in. - Output: changed files, every conflict with its marker text, the migration script, key conflicts, new env vars the target lacks, missing resources, and targetVersion / sourceVersion for start_merge. - With no conflicts it also starts the pre-merge checks in the background. Neither branch is changed. - Conflicts: a merge from x into y edits y; a merge into main edits the source branch (main is never edited by a merge). Fix each conflicted file there with edit_file / apply_patch so it holds both sides' changes. - When to use: the user asks to merge branches, what a merge would change, or to fix a failed merge. Flow: compare_branches → read_merge_conflict and fix each conflict → static/__dev/migration.js if the database or storage must change (get_guides("fork")) → compare_branches → start_merge → get_merge_status.

NameTypeReqDescription
projectIdstringyes–
sourceProjectIdstringyes–

No output schema declared.

No examples provided.

compare_published_source ~107

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.

NameTypeReqDescription
diffsarray–Paths to diff.
offsetinteger––
projectIdstringyes–
releasestring–Release id. Default: live.

No output schema declared.

No examples provided.

copy_file ~85

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.

NameTypeReqDescription
copiesarrayyes–
expected_versioninteger––
projectIdstringyes–

No output schema declared.

No examples provided.

create_checkpoint ~163

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 (e.g. 'Added login page with email auth'), optionally a description with detail. No-op when nothing changed since the last checkpoint. Restoring a checkpoint reverts code and project config only — database rows, uploaded assets and published deployments are not rolled back.

NameTypeReqDescription
descriptionstring––
projectIdstringyes–
titlestringyes–

No output schema declared.

No examples provided.

create_project ~189

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> in list_files). The result renders a live preview card for the user and includes the first-build playbook: a fresh project is EMPTY until pages are written, so a session normally continues straight into get_guides("design") and the first page rather than ending at the card.

NameTypeReqDescription
initial_promptstringyesA description of the app to build, in the user's own wording where they gave one. Stored as the project's system prompt.
namestringyes–

No output schema declared.

No examples provided.

delete_branch ~62

Permanently delete a branch: its files, database copy and comments (merged code stays). Only when the user asked. A branch not merged into main needs discardUnmerged: true.

NameTypeReqDescription
discardUnmergedboolean––
projectIdstringyes–

No output schema declared.

No examples provided.

delete_file ~79

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.

NameTypeReqDescription
expected_versioninteger––
pathstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

delete_storage_file ~144

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 deleted: to stop using a file, remove its reference from the code instead. Needs edit access to the project.

NameTypeReqDescription
keysarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

edit_file ~114

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.

NameTypeReqDescription
expected_versioninteger––
new_strstring––
new_stringstring––
old_strstring––
old_stringstring––
pathstringyes–
projectIdstringyes–
replace_allboolean––

No output schema declared.

No examples provided.

execute_sql ~302

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 one connection in one transaction that Floot opens and commits: if any statement fails, or the query times out before its COMMIT, nothing is applied. Leave BEGIN/COMMIT/ROLLBACK out of the query — a COMMIT or ROLLBACK inside it ends that transaction early, so a later failure no longer undoes what came before. Set no_transaction for statements that cannot run inside a transaction block (VACUUM, CREATE INDEX CONCURRENTLY, …); each statement then applies as it finishes. Queries are stopped after 75 seconds either way; split a longer migration into several calls. A disconnect does not stop a call that has started: if you got no result, check the schema before running it again.

NameTypeReqDescription
databasestring––
no_transactionboolean–Run the statement without a wrapping transaction — required for VACUUM, CREATE INDEX CONCURRENTLY, and other statements Postgres rejects inside a transaction block.
projectIdstringyes–
querystringyes–

No output schema declared.

No examples provided.

fetch ~59

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

fork_project ~270

Fork a project (main or any fork) into a new branch with its own database branch and test keys, when the user asks to fork, branch, or try changes away from the project. - Forks at once; no confirmation. - copyFlootDb (default "full"): "full" the parent's data. "schema": same tables, no rows. "pointInTime" + databaseAt (ISO 8601 with zone): the parent's database as it was then (code, files, keys stay current), to recover older data. - isolated true (only if asked): empty tables; no real data, keys or stored files (the /_cdn/static assets still show). - scratch true: a throwaway branch (QA run, rehearsal, backup copy): cannot be merged, deleted after 7 idle days unless kept. - Output: fork project id and preview link. Merge back with compare_branches, then start_merge. Code that breaks on a fork: get_guides("fork").

NameTypeReqDescription
copyFlootDbstring––
databaseAtstring––
isolatedboolean––
namestringyes–
projectIdstringyes–
scratchboolean––
suggestedCopyFlootDbstring––

No output schema declared.

No examples provided.

generate_image ~161

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 goes in with upload_asset. To edit or restyle an image, or keep a character, product or logo consistent, pass it in reference_images (this project's stored assets only: upload an outside image or the user's photo first) and say in the prompt what to change.

NameTypeReqDescription
imagesarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

get_analytics ~140

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').

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD (UTC). Default: the 30 days ending on to.
limitinteger–Rows per list (default 25).
projectIdstringyes–
tostring–Last day, YYYY-MM-DD (UTC), included. Default: today.

No output schema declared.

No examples provided.

get_branch_settings ~156

Read a branch's six switches (all off by default): Receive main's email, Send email, Scheduled jobs, Receive main's realtime messages, Send realtime messages to main, Queued jobs. Lists only those the branch's code uses, as the UI does. - When to use: a branch sends or receives no email, its scheduled or queued jobs don't run or run twice, or realtime messages or presence aren't shared with main. - The user changes them in the branch's Project Settings › Advanced (branch creator or project owner). On an isolated branch, scheduled_jobs sets Scheduled jobs; to run one job now, call_app_function's scheduled_job.

NameTypeReqDescription
projectIdstringyes–
scheduled_jobsboolean––

No output schema declared.

No examples provided.

get_current_context ~230

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.). Call this FIRST when the user refers to something without naming it ("this", "here", "the button"), reports a problem without saying where ("it's broken", "looks wrong"), or implies they triggered something in Floot ("go", "I clicked fix", "I undid that"). Cheap and text-only. With several windows open, one answers (the result says which) — but a selection made in ANY window is merged in, so a "no selection" from the answering window plus a deposited selection from another window means the deposited one is what the user means. If it reports a pending annotation, call view_annotation to see the image.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

get_guides ~148

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 with a projectId — pass projectId whenever you're working on a project; idempotent, never overwrites existing files.

NameTypeReqDescription
projectIdstring––
topicstring––
topicsarray––

No output schema declared.

No examples provided.

get_job_status ~142

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 request means a fresh call on the originating tool, never re-polling an old jobId. Legacy v!/b! job ids are also accepted.

NameTypeReqDescription
jobIdstringyes–
wait_secondsinteger––

No output schema declared.

No examples provided.

get_live_payments ~385

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-payments') before your first call. Responses follow Stripe API version 2026-08-26.dahlia.

NameTypeReqDescription
created_gteinteger–List filter: created at or after (unix seconds).
created_lteinteger–List filter: created at or before (unix seconds).
customerstring–List filter (without projectId): a customer id.
expandarray–Stripe expand, e.g. ["latest_charge"].
idstring–A Stripe object id (pi_…, ch_…, cs_…, sub_…, in_…, cus_…, re_…) to read that one record. Omit to list.
limitinteger––
modestring–"live" (default): the published app's real payments. "test": test payments made in the preview.
objectstringyesThe record type to read.
pagestring–Project-limited list paging: next_page from the previous result.
projectIdstring–Limit a list to one project (runs as a Stripe search on that project)
querystring–Stripe search query for a project-limited list, e.g. status:"succeeded".
starting_afterstring–List paging: the last id of the previous page.
statusstring–List filter (without projectId): a status.

No output schema declared.

No examples provided.

get_logs ~393

Call FIRST when debugging a runtime problem (a 500, a failed request, a blank page, 'it doesn't work'), before theorizing. Sources: - '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. - 'browser': console output and client network requests (`⇄ METHOD url → status`, error body of failed ones: CORS, timeouts, third-party calls) from the user's open editor (~1 hour; empty if none); a line's `ref=<id>` is a 'server' log_reference_id. - 'background': background work in the preview and the published app: schedules and next run, runs in progress, runs long or cut off at the 15-minute limit in 7 days ('still running?', 'timed out?'). - 'published': the PUBLISHED app's backend logs (kept 90 days), oldest first, last hour by default; from/to (ISO 8601), filter (literal substring), limit (default 200), cursor (get_guides('prod-backend-logs')). - 'push': push sends, newest first, per device, delivered or not; from/to, subscription (one device's endpoint), cursor. - 'email': the test inbox: mail kept unsent (branch with Send email off; preview sends to test addresses like qa+1@example.com) and other preview sends, as text with links (sign-in codes, reset links).

NameTypeReqDescription
cursorstring––
filterstring––
fromstring––
limitinteger––
log_reference_idstring––
projectIdstringyes–
sourcestring––
subscriptionstring––
tostring––

No output schema declared.

No examples provided.

get_merge_status ~70

State of a merge by mergeId (merges started in the UI too): running, done or failed. On failed: the failing step or migration script and its exact error. On done: the keys added to the target and the passed pre-merge checks.

NameTypeReqDescription
mergeIdstringyes–

No output schema declared.

No examples provided.

get_preview_url ~381

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 its query string and only works shared EXACTLY as returned (no Floot login, view-only — which is also what lets it open on a phone); it live-updates as you edit, so it also suits an in-app browser tab if your client has one. The result additionally includes the sandbox API base for your own headless /_api/* testing — the frontend does not render there and it is not a user-facing URL; the preview link is the one meant for the user. Floot hosts the app: publish_app publishes it to production. To send the user straight to one view (a page, a component's examples, a page's staged screens, a design canvas or one of its frames, a page's link preview card), pass targetType with path or name, as navigate_preview takes them: the link then opens on that view, with or without a Floot window open.

NameTypeReqDescription
namestring–The other targetTypes: the item name as list_files shows it, with "#<screen>" for page examples or "#<section, frame or bookmark id>" for a design ("CheckoutExplorations#payment").
pathstring–targetType "page" or "link-preview": a path from "/", query and hash allowed.
projectIdstringyes–
targetTypestring–Optional: the view the link opens on, as navigate_preview's targetType. Omit for the plain preview.

No output schema declared.

No examples provided.

get_publish_status ~376

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 monthly iOS/Android app-build allowance; `unlimited` is true on plans where the ceiling is only a fair-use backstop, and while an Action Boost is live (`boostUntil` says until when; builds started before then never count toward the allowance) — read this BEFORE passing mobile: true, and on a metered plan build only when the user asked for a native/TestFlight/Play build), displayFlootLogo (whether the live app shows the 'Made with Floot' badge; true until a paid owner turns it off), and mobileBuild (the project's latest native app build: building, succeeded, or failed with what to fix; on a succeeded build, storeBuilds says how each store's build and upload went (building, live, or failed), which can fail after the native build succeeded; isMobileTestMode marks a mobile test build — an app build finishes minutes AFTER the publish job it rode on, so read this to learn how it ended before telling the user it worked). This is the ONLY tool that reports attached custom domains — read it before telling a user whether their domain is connected, and never conclude a domain is unattached from any other output. The publish card calls this on load to render fresh state; also check it before publishing to know whether publish_app will publish fresh or publish the live app again.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

list_branches ~71

List a project's main project and every branch you can open, with their ids, names and status. projectId may be the main project or any of its branches. - When to use: the user names a branch of a project, or asks which branches it has.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

list_files ~102

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 changes them.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

list_projects ~91

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.

NameTypeReqDescription
limitinteger––
name_filterstring––

No output schema declared.

No examples provided.

list_resources ~159

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 any credential (the owner may already have the one you need). Pass query (case-insensitive substring over names, descriptions, types, and env var names) to filter when the account has many resources. Read-only. Details: get_guides('resources').

NameTypeReqDescription
projectIdstringyes–
querystring––

No output schema declared.

No examples provided.

navigate_preview ~368

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. "design": the canvas designs/<name>.tsx fitted, listing its sections and frames; "#<id>" zooms to one. "link-preview": the link preview card (pages/<page>.ogImage.tsx) of the page at `path`, with its verdict. "merge-review": the merge review of branch projectId, into main or the branch id in `name`; only in the user's own signed-in window, otherwise it fails and returns a link to it. Needs a Floot window open for this project; fails fast otherwise.

NameTypeReqDescription
namestring–The item name as list_files shows it, no folder or extension: "HeroSection", "dashboard", "_index", "user.$id", page examples with "#<screen slug or title>" ("dashboard#empty-state"), or a design wit…
pathstring–targetType "page" or "link-preview": a path from "/", query and hash allowed ("/user/123?tab=settings#top"; pages/user.$id.tsx serves /user/<id>).
projectIdstringyes–
targetTypestringyes–

No output schema declared.

No examples provided.

provision_resource ~899

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: - 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/…

NameTypeReqDescription
actionstring–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_functionsarray–Only for resource "app-connection": the exact function names this project needs from the other app's helpers/flootAppExports.tsx.
app_notestring–Only for resource "app-connection": one sentence for the user on why this project needs these functions. Shown in the confirmation dialog.
app_targetstring–Only for resource "app-connection": the OTHER Floot app — its project id, name.floot.app address or custom domain.
projectIdstringyes–
resourcestringyes–

No output schema declared.

No examples provided.

publish_app ~499

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 in Stripe live mode): never ask the user test or live; mobile test builds are started by the user on floot.com. If the owner has not finished Stripe setup (payments) or connected Shippo (shipping), the publish is refused with a card to do it (nothing published): tell the owner to click it, then call publish_app again.

NameTypeReqDescription
add_anotherboolean–custom_domain only: the user explicitly asked for an ADDITIONAL custom domain. Without it, a project that already has domains gets those domains back instead of the wizard.
domainstring–floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit on a live app (it keeps its subdomain); omitted on a first publish, the user gets the publish form; on a published app…
domain_typestring–Omit for the floot subdomain. 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts.
include_made_with_flootboolean–false removes the 'Made with Floot' badge (paid plans only — fails for free accounts). Omit to keep the current setting.
mobileboolean–true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, a native or mobile app, or a phone build. No store connected → a Connect card (nothing published); connected → the…
projectIdstringyes–

No output schema declared.

No examples provided.

pull_database_schema ~179

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/external database. The helper is GENERATED — never hand-edit it or cast around its types: if a column's type is too loose (e.g. role as string when code expects "user" | "admin"), fix the DATABASE (CREATE TYPE … AS ENUM + ALTER COLUMN … TYPE) and re-pull, and the union type falls out.

NameTypeReqDescription
databasestring––
helper_namestring––
projectIdstringyes–

No output schema declared.

No examples provided.

query_database ~121

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.

NameTypeReqDescription
databasestring––
projectIdstringyes–
querystringyes–

No output schema declared.

No examples provided.

read_file ~432

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 lists the files that reference this one (imports, queueTask/runCode names, endpoint URL strings): check it before renaming or deleting, or use rename_file, which rewrites importers. Hosted assets read too (/_cdn/<name> as upload_asset / generate_image return it, private/<name>): png/jpeg/gif/webp come back as an image you can see (≤3.75 MB), text as text, other binaries as a summary. No typecheck by default: diagnostics:"auto" appends a .ts/.tsx file's current type errors when the VM is warm, "wait" boots it and forces the check. older_than walks the file's history: "current" shows it just before its latest change, the returned cursor steps further back; restore by writing the old content with write_file.

NameTypeReqDescription
columninteger––
diagnosticsstring––
include_referencesboolean––
limitinteger––
offsetinteger––
older_thanstring–Omit (or leave empty) to read the current file. Set it only to read the file as it was BEFORE an earlier change. Pass "current" for the version just before the latest change to it, then the cursor ea…
pathstringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

read_files ~284

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 name. With older_than (up to 5 paths) the files are walked back through history TOGETHER on one timeline — the way to keep a component and its stylesheet consistent.

NameTypeReqDescription
diagnosticsstring––
include_referencesboolean––
limitinteger––
older_thanstring–Omit (or leave empty) to read the current file. Set it only to read the file as it was BEFORE an earlier change. Pass "current" for the version just before the latest change to it, then the cursor ea…
pathsarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

read_merge_conflict ~134

Read one conflicted file of a merge in pages (cat -n style, 400 lines by default), with its conflict block line ranges. projectId is always the TARGET (the branch merged into); sourceProjectId is the branch merged in. - view: "markers" (the file with conflict markers; default), "source" or "target" (that branch's current file).

NameTypeReqDescription
limitinteger––
offsetinteger––
pathstringyes–
projectIdstringyes–
sourceProjectIdstringyes–
viewstring––

No output schema declared.

No examples provided.

remove_dependency ~40

Remove npm packages from a Floot project's dependency record (record-only; nothing runs).

NameTypeReqDescription
packagesarrayyes–
projectIdstringyes–

No output schema declared.

No examples provided.

rename_file ~122

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 one rename's target is another's source).

NameTypeReqDescription
expected_versioninteger––
projectIdstringyes–
renamesarrayyes–

No output schema declared.

No examples provided.

request_external_resource ~358

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 connects. Never ask the user to paste a secret into the chat.

NameTypeReqDescription
instructionsstring–Why the key is needed / where the user can find it — shown to the user in the dialog.
namestring–Display name. GENERIC: the service, e.g. 'Stripe'. POSTGRES: the database's name; the user's dialog opens with it and the env var is derived from it ('Reporting DB' gives REPORTING_DB_CONNECTION_STRI…
optional_env_varsarray–GENERIC only: env vars the user can leave blank and fill in later, e.g. a webhook signing secret.
projectIdstringyes–
reuse_existingboolean–Default true: a matching credential the owner already saved (same name or env var) is attached without asking the user. Pass false when this project needs its OWN, separate credential (a test or copi…
secret_env_varsarray–Required for GENERIC: the env var name(s) your code reads, e.g. ["STRIPE_SECRET_KEY"]. Each is a required field in the user's dialog.
typestringyes–

No output schema declared.

No examples provided.

request_user_upload ~372

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 machine, or a user-provided file you hold but can't upload yourself (over the 3 MB inline cap with no S3 egress — the card uploads from their browser, which is never egress-blocked). Returns a jobId — poll get_job_status; it stays running until they upload, then returns the publicUrl to reference in code. When you show the card, tell the user in a sentence why you're asking — e.g. that you can see their image but the file itself doesn't reach Floot, so re-adding it here is a one-click step — and ask them to say "uploaded" when done in case your polling ends before they finish. For files you hold yourself, use upload_asset; for AI-generated imagery, use generate_image. Some clients can't show the card (Microsoft Copilot Studio, for one): if the user says they don't see it, give them the project's preview link (get_preview_url) and ask them to sign in there and drag the file into Storage › Static (or use its Upload button), then call list_files — the file is listed under "Files uploaded in the editor" with the /_cdn/static/ path to use.

NameTypeReqDescription
descriptionstring–Shown in the card — what you're asking for, e.g. "the logo image you attached".
projectIdstringyes–

No output schema declared.

No examples provided.

run_code_in_browser ~417

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) work. A `_floot` global has `storageUpload({ filename, contentType, sizeBytes })` to save a file the page made (e.g. a canvas as a PNG: it returns a presignedUrl to PUT the bytes to and the file's url), `storageGetUrl(key)` and `getFileById(id)` to load a stored or uploaded file into the page, and `navigate(path)` to move the preview to another route first. Needs the project open in the editor (fails fast otherwise); prefer run_code_in_vm when the DOM is not needed. A snippet gets 20 seconds, fixed (there is no timeout argument); past that the call fails while anything the snippet started keeps running. So never wait on a slow /_api/* endpoint here: call it from run_code_in_vm (timeout_seconds up to 120), and for longer work have the endpoint start a background task and poll (get_guides("queueTask")). Typed text input and long multi-step flows are unreliable here: leave those to the user.

NameTypeReqDescription
codestringyesA TypeScript module that exports a default async function returning a string; that string is the tool result. Runs at the project root, so import other files by relative path. No top-level `return` (…
projectIdstringyes–

No output schema declared.

No examples provided.

run_code_in_vm ~481

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. For data too large to pass through the conversation (an uploaded CSV, images, usage and log history), a `_floot` global works on this project only: - `runSQLQuery({ query, reasonAndExplanationForNotReadOnly? })`: runs SQL on the project's database. Read-only unless a reason is given; then the whole query is one transaction, and DELETE/UPDATE/TRUNCATE/DROP are refused. A call already sent is not cancelled when the snippet times out (guide vm-sql). - `getFileById(id)`: the download URL of a file the user uploaded. - `storageList(prefix)`, `storageGetFileSizes(visibility, continuationToken?)`, `storageGetUrl(key)`: the project's stored files, their sizes, and one file's download URL. - `storageUpload({ filename, contentType, sizeBytes })`: an upload URL for a new public file, and the URL it will have. - `getHostingUsage({ days? })`, `getLambdaUsage({ days? })`: the project's daily hosting and compute usage. - `getProdBackendLogs({ filter?, from?, to?, nextToken?, limit? })`, `getPushHistory({ subscription?, from?, to?, offset? })`: the published app's logs and push sends, to count or search in code. - `paymentsTestRequest({ method, path, params? })`: a Stripe request as the preview's stripeRequest makes it (test mode, project owner only; guide live-payments). For a one-off read use query_database or get_logs; for other SQL, execute_sql; to delete files, delete_storage_file; to run one of the app's exported functions, call_app_function. Guides: vm-sql, static-storage, hosting-cost-analysis, prod-backend-logs.

NameTypeReqDescription
codestringyes–
projectIdstringyes–
timeout_secondsinteger––

No output schema declared.

No examples provided.

run_tests ~285

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/testEnv.tsx setting process.env.JWT_SECRET = "test-secret"; env is reset per spec file), spyOn cannot replace an exported function of a project module (pass dependencies in as arguments instead), no top-level await in specs, and @floot/* services (email, storage, ai, queueTask, …) never run: each function is a Jasmine spy that throws until the spec gives it a result on the imported function itself, e.g. (sendEmail as jasmine.Spy).and.resolveTo({ ok: true, messageId: "m1" }); spies reset before every spec. Returns per-file PASS/FAIL with failing expectations. Defaults to all spec files except hook specs (file name contains "use" — those need real React scheduling and are excluded, matching the in-editor checker); pass `paths` to run specific spec files, including hook specs.

NameTypeReqDescription
pathsarray––
projectIdstringyes–

No output schema declared.

No examples provided.

screenshot_preview ~213

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 build a separate "mobile" page or example just to look at a narrow layout.

NameTypeReqDescription
projectIdstringyes–
viewportstring–Device to capture on: "desktop", "iphone-15", "pixel-7", "ipad" — the preview's own device presets (Desktop, iPhone (393×852), Pixel (412×915), iPad (820×1180)) — or a custom "WIDTHxHEIGHT" such as "…

No output schema declared.

No examples provided.

search ~47

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.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the com.floot/floot MCP server?

com.floot/floot is a hosted endpoint at https://mcp.floot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.floot.com

# add to Claude Code
claude mcp add --transport http com-floot-floot 'https://mcp.floot.com/mcp'
Common questions

What is the com.floot/floot MCP server?

com.floot/floot is an MCP server listed in the public MCP registry as com.floot/floot. Build and publish full-stack web and mobile apps on Floot from any MCP client. Building is free. This page covers its hosted endpoint (https://mcp.floot.com/mcp).

Is the com.floot/floot MCP server safe to use?

com.floot/floot scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.floot/floot MCP server expose?

com.floot/floot exposes 58 tools: search, fetch, list_projects, list_resources, list_files, and 53 more. Their descriptions and schemas cost roughly 13,138 tokens of context every time the server is loaded.

Does the com.floot/floot MCP server require authentication?

Yes. com.floot/floot asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the com.floot/floot MCP server still maintained?

com.floot/floot is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.floot/floot MCP server?

VerifyMCP ran 14 checks on com.floot/floot, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.