Connect MCP

Floo is an MCP server. Add it to the agent you already use and the agent can design on your canvases, read comments, and study real app screens, acting as you.

Server addresses

There are two servers. Both use the same sign-in and act as the same person; pick the one you need, or add both.

Both are remote servers that use the Streamable HTTP transport. If a client asks for a transport type, choose HTTP (sometimes called "Streamable HTTP" or http), not SSE or stdio.

Signing in

• OAuth (recommended). The first time a client connects, a browser tab opens. Sign in to Floo and approve the client. From then on it works as you, with exactly your access, and you can disconnect it any time in Settings → Agent keys → Connected apps.
• Agent key. For clients that can't open a browser (n8n, CI, scripts, servers), create a key in Settings → Agent keys and send it as a header: Authorization: Bearer cvk_…. See Agent keys.

Pick your agent

The Connect agent dialog on every canvas walks through the most common ones with the address filled in, and turns green when your agent arrives.

The generic entry

Most clients that read a JSON file accept this. The name floo is only a label on your machine; any name works.

{
  "mcpServers": {
    "floo": {
      "type": "http",
      "url": "https://worker.floo.design/mcp"
    }
  }
}

Point it at a canvas

Paste the starter message from the Connect agent dialog as your first message. It names the canvas, and the agent fetches everything else from Floo:

Work on Floo canvas cnv_8hQ2x. Start with get_guide and follow it.

Agents read get_guide first: it explains how frames work, how to work alongside people and the quality bar. Every tool is listed in MCP tools.

Troubleshooting

• 401 or "unauthenticated". The client hasn't signed in yet. Run its sign-in step (for example /mcp → Authenticate in Claude Code), or check that an agent key header is exactly Authorization: Bearer cvk_….
• The browser sign-in never opens. Some clients only support OAuth in newer versions. Update the client, or use an agent key.
• "Method not allowed" on GET. Expected: the servers are stateless and only answer POST requests. Make sure the client is set to HTTP, not SSE.
• A cloud client (claude.ai, ChatGPT) can't connect. They reach the server from the internet, so the address must be public HTTPS. A Floo running on localhost only works with clients on your own machine.
• The agent can see a canvas but not change it. Agents have your access: on a canvas you can only view or comment on, they can too.