Connect an MCP client to the local, token-gated bridge in the flowmo desktop app, then verify that it is driving the intended installed or development app.
Where: flowmo desktop app → project menu or create surface → Connect to Claude
Before you start
- Install and launch the flowmo desktop app.
- Install Claude Code, Claude Desktop, or another MCP client. The one-click button currently writes Claude configurations.
Key ideas
- Desktop bridge: MCP control is provided by the desktop app. The installed app exposes its local automation server on port 17765; a development app uses 17766 so both can remain connected without crossing over.
- One-click registration: Connect automatically merge-writes only flowmo’s MCP entry into Claude Code and an installed Claude Desktop configuration, preserving other servers, and installs the bundled flowmo skills.
- Local authentication: The bridge binds to 127.0.0.1 and requires the app-generated automation token. The registered entry pins the matching app URL and token file; the user does not paste a token into chat.
Steps
- Open the flowmo desktop app and the project you want the external AI to control.
- Open Connect to Claude and choose Connect automatically. The live app registers as f0; a development app registers as f0-dev.
- Restart the MCP client so it reloads its server configuration and bundled skills.
- In the MCP host, call f0_health first. Confirm that the expected app and project tab are listed before making changes.
- Use f0_catalog or f0_features to discover the relevant feature, then f0_list_tools for the target surface before invoking a tool.
Live and development connections
- f0: installed flowmo app, port 17765, packaged app token directory.
- f0-dev: local development app, port 17766, development token directory.
- Both entries pin their own URL and token file; do not rename f0-dev to f0.
Manual clients
A non-Claude MCP client can launch the same stdio server. Point it at the packaged/source server and pin F0_AUTOMATION_URL plus F0_AUTOMATION_TOKEN_FILE to the intended app. Treat the token as a local secret.
Limitations and important notes
- The Connect to Claude menu is Electron-only and does not appear in the browser build.
- Restarting the MCP client is required after registration.
- Remote MCP needs separate IAM and service-token configuration; it is not the normal local setup.
Troubleshooting
f0_health cannot reach flowmo
Confirm the desktop app is running, restart the MCP client, and check that the connection targets 17765 for installed flowmo or 17766 for the development app.
The host controls the wrong app
Use the f0 versus f0-dev server explicitly. Re-run Connect automatically from the intended app so its entry is pinned to the correct URL and token file.
The connection reports an authentication error
Do not copy a token into the prompt. Reconnect from the app so the MCP entry points at the current automation-token.txt, then restart the client.