What your AI can do
The full capability list for the Floot connector — what your assistant does on its own, and the few things you finish in the browser.
Once Floot is connected, your AI assistant has one set of tools for reading, writing, running, and publishing your Floot projects. This page is the honest list: what it can do, what it cannot, and where the line falls.
Not connected yet? Claude and ChatGPT install Floot in one click — see Build from Claude & ChatGPT. For everything else, see Connect any MCP client.
Every client gets the same tools
Floot does not offer a reduced tool set to any client. Standard ChatGPT is the one case that looks like it does — it can call only tools named search and fetch, which is ChatGPT's own contract for standard mode. See Connector troubleshooting.
Capability matrix
| Task | Your AI assistant | How |
|---|---|---|
| Create a project | Yes | create_project makes a new Floot project and returns its id. |
| Read your code | Yes | list_files, read_file, read_files, search_code. |
| Write and edit code | Yes | write_file, edit_file, apply_patch, rename_file, copy_file, delete_file. |
| Add or remove npm packages | Yes | add_dependency and remove_dependency, validated against Floot's supported set. |
| Add a database, auth, or a login provider | Yes | provision_resource creates Floot-managed resources server-side and seeds the code. There are no keys to paste. |
| Run SQL | Yes | query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers. |
| Read runtime logs | Yes | get_logs — the first step for any 500, blank page, or failed request. |
| Typecheck and run tests | Yes | typecheck, and run_tests for the project's Jasmine specs. |
| Run code | Yes | run_code_in_vm runs a Node snippet on the project's VM; run_code_in_browser runs inside the live app to read its DOM. |
| Show you the app | Yes | get_preview_url returns a live link, screenshot_preview captures the screen, navigate_preview points your open preview at a page or component. |
| See what you are looking at | Yes | get_current_context reads your open project view — selected element, current page, whether you drew an annotation; view_annotation opens the drawing. |
| Generate images | Yes | generate_image writes AI images into the project. This is the one action that also spends Floot credits. |
| Take a file from you | Yes | request_user_upload shows an upload card you pick a file in; upload_asset uploads bytes it already holds. |
| Ask for an API key | Yes, through your browser | request_external_resource creates the request and hands you a floot.com link. Keys never travel through the chat, and your assistant only learns the environment variable name. |
| Publish, republish, unpublish | Yes | publish_app, republish_app, unpublish_app, and get_publish_status. Publishing runs the same code as the Publish button in the Floot web app. |
| Name a restore point | Yes | create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view. |
| Change project settings | Yes | update_project_metadata — title, description, icon, splash, server-side rendering, iOS Info.plist strings. |
| Set up a custom domain | Starts it, you finish it | publish_app creates the request and gives you a link to the wizard. |
| Turn on native mobile app builds | No — you do this yourself | There is no tool and no publish parameter for it. Open the project on floot.com, click Publish, and switch on Generate native mobile apps. |
| Download the code export zip | No — you do this yourself | The zip is assembled in your browser. Open the project menu on floot.com, choose Get Code, then Download as ZIP. |
| Buy anything or change your plan | No — you do this yourself | There is no checkout tool. Plans and purchases are pages on floot.com you open and buttons you click — start at the plan page. |
Turning on native mobile app builds
Your assistant cannot turn this on. There is no tool and no publish parameter for it, so rephrasing the request will not help. If mobile builds are already switched on for an app, a republish keeps them on — your assistant just cannot be the one to enable them.
You switch it on yourself. Open the project on floot.com — any preview link your assistant hands you from get_preview_url goes there, and signed in as the owner you get the full Publish dialog. Click Publish, then under Native App Store Apps switch on Generate native mobile apps. Native mobile builds need the Power plan (or an older plan with a quota of 100,000 credits a month or more). See Creating mobile apps.
Setting up a custom domain
Your assistant can start a custom-domain setup but cannot complete one — DNS setup needs you. Ask for a domain and it calls publish_app, which creates a request and gives you a floot.com link to open. The app has to be live on a .floot.app subdomain first.
The request stays open for one hour and only one can be pending per project. If it expires, ask again and your assistant creates a fresh one. It is not blocking — your assistant can carry on with other work while you finish the wizard.
Opening the link takes you to your project with the Add Custom Domain wizard already open. Enter the domain and add the DNS records it shows you. Custom domains are a paid feature, resolved against the project's owner — a paid collaborator on a free owner's project still cannot attach one. See How to add a custom domain.
Getting your code out
Your assistant cannot produce the export zip — it is built in your browser, not on Floot's servers. What it can do is read any file in the project with read_file, read_files, and search_code, so asking it to print or copy specific files works fine.
For the whole project as a file, open the project menu on floot.com, choose Get Code, then Download as ZIP. Code export is a paid-plan feature — see Code, data, and exports.
No tool can spend your money
Nothing your assistant can call buys anything. There is no checkout tool, no plan-change tool, and no way for an agent to add a payment method or top up an account. Every purchase on Floot is a page you open and a button you click. This is deliberate, not an oversight: an agent must never be able to spend your money by calling a tool.
The one thing a tool can consume is Floot credits you already have, and only through generate_image. Those credits come off the project owner's account rather than whoever is driving the chat — so building in someone else's project spends their credits, not yours. Everything else is metered in build actions, which come with your plan.
Projects other people shared with you
Your assistant can read and edit any project you own. A project another Floot user shared with you needs a paid Floot plan on your own account before the connector will open it, for reading or writing — any paid plan does, not one specific tier. Public projects stay readable by anyone; write access never rides on a project being public.
How your assistant learns Floot's conventions
Floot ships its own documentation to your assistant through the get_guides tool — an overview, design guidance, a first-build walkthrough, backend primitives, publishing, resources, and more. If a build starts drifting away from how Floot works, telling your assistant to read the relevant guide is usually faster than explaining the conventions yourself.