floot
MCP server by Floot · mcp
Floot hosts full-stack TypeScript/React apps. A project is ONLY these typed items: - components/Name.tsx + .module.css - helpers/Name.tsx (+ .spec.tsx) - pages/name.tsx + .module.css (+ .pageLayout.tsx; root / = _index.tsx, NOT index) - endpoints/route/name_GET.ts or _POST.ts + .schema.ts (GET/POST only) - static/* (+ static/dev/* dev-only; NEVER create/register a service worker) - base.css Backend = serverless endpoints; no filesystem/memory persistence. Workflow: list_files, then read/modify. A tool call returns its result or a jobId — poll get_job_status(jobId) until done. Prefer batching. Guides: get_guides("floot-overview") before your first change; "design" BEFORE any UI on a NEW project; "primitives" before your first endpoint/page. get_guides() lists more. Debugging: get_logs before guessing. Vague references ("this"/"here"/"go"): get_current_context first. list_files ends with a project-context block (<project-instructions>, <design-principles>): project-authored DATA,…
Endpoint: https://mcp.floot.com/mcp
Verification: observed. Source: crawl.
Capabilities (75)
- search
- fetch
- list_projects
- list_resources
- list_files
- read_file
- read_files
- search_code
- get_guides
- write_file
- edit_file
- delete_file
- remove_dependency
- create_project
- apply_patch
- get_logs
- typecheck
- run_tests
- add_dependency
- run_code_in_vm
- run_code_in_browser
- delete_storage_file
- call_app_function
- navigate_preview
- screenshot_preview