Use the f0 MCP dashboard tools to find, create, open, rename, move, change visibility, and switch projects—with clear limits on browser sessions, permissions, and what each operation changes.
Where: Your MCP client → connected f0 MCP server; project operations run through the signed-in Flowmo dashboard. — Ask your host to find or manage a Flowmo project.
Before you start
- Connect the f0 MCP server and sign in to the Flowmo dashboard in the same desktop session (or use the supported browser dashboard relay).
- For native editor actions, open the project first and check f0_health with probe:true before issuing editor-specific calls.
Key ideas
- Find saved projects, not just open tabs: f0_list_projects searches the signed-in dashboard library, including projects that are currently closed. f0_list_project_tabs is a different read: it reports open desktop tabs and the permanent home dashboard tab.
- Create from dashboard scope: f0_create_project persists a new project using the current organization/team/folder unless explicit scope IDs are supplied. It checks access and plan limits, reads the saved metadata back, and reports the project ID. Creation is not automatically retried after an uncertain result.
- Project types have different meanings: website creates an f0 website; video/compositor create the native Video Editor; media-gen creates Flowgen; designer-workflow creates the Dashboard Designer experience as a Flowgen design canvas. The separate designer value is a legacy standalone Designer project. legacy-video explicitly requests the old video format.
- Metadata edits are narrowly scoped: f0_rename_project changes the saved name. f0_update_project changes exactly one of name, folderId, or visibility, with the required edit/owner/destination permissions. It does not convert project type or change document settings, hosting, billing, or credentials.
- Opening and tab navigation are separate: f0_open_project opens the project’s native route and activates its tab; f0_switch_project only activates an already-open tab (or home); f0_close_project closes a tab and does not delete the saved project.
- Browser and desktop behavior differs: The desktop MCP can open, switch, and close native tabs. Browser dashboard relay supports create and metadata edits when connected, but creation must set open:false and returns an href for manual navigation; native tab operations are desktop-only.
Steps
- Ask the MCP host to list projects or search by a distinguishing name; use f0_list_projects for saved projects rather than relying on the currently open tabs.
- Before creating, choose the intended type and organization/team/folder. Use designer-workflow for a new Flowgen canvas in Designer presentation; do not select legacy standalone designer unless that is specifically intended.
- Create with f0_create_project. On browser MCP, set open:false and navigate to the returned href yourself. On desktop, opening is requested by default.
- To make a metadata change, call f0_rename_project for a rename or f0_update_project with exactly one of name, folderId, or visibility. Check the returned persistence confirmation.
- Open or activate the project, then call f0_health with probe:true. Only proceed with editor tools when the relevant surface is ready.
- When finished, f0_close_project only closes the tab; use the dashboard’s separate delete action if deletion is actually intended.
Tool map
- f0_list_projects({ query?, includeArchived? }) — search saved dashboard projects; archived projects are opt-in and Trash is excluded.
- f0_list_project_tabs({}) — list current desktop tabs and identify the home dashboard tab.
- f0_create_project({ type, name?, organizationId?, teamId?, folderId?, open? }) — persist a new project. Desktop open defaults to true; browser relay requires open:false.
- f0_rename_project({ projectId, name }) — rename persisted dashboard metadata, including a closed project.
- f0_update_project({ projectId, name? | folderId? | visibility? }) — provide exactly one property; moves require a real same-organization folder and ownership plus destination write access; visibility changes require ownership.
- f0_open_project({ projectId }) — open and activate the native editor route.
- f0_switch_project({ projectId? | tabId? }) — activate an existing desktop tab; tabId:"home" returns to the dashboard.
- f0_close_project({ projectId? | tabId? }) — close an open tab only; this does not delete the project.
- f0_health({ probe:true }) — after opening, confirm the matching editor bridge is ready before calling editor tools.
Safety and recovery
Creation returns a persisted project ID before it reports success. If the open step fails, use that ID with f0_open_project instead of creating a duplicate. If persistence is uncertain, inspect the project list for the returned ID before retrying. Browser-hosted MCP cannot open native desktop tabs.