Docs
Documentation
Back to FlooGet started
Getting started
  • Your first canvas
  • The canvas editor
Agents
  • Connect an agent
  • The Floo Agent
  • MCP tools
Connect MCP
  • Claude Code
  • Claude
  • ChatGPT
  • Codex
  • Cursor
  • VS Code
  • Windsurf
  • Gemini CLI
  • Other clients
  • Agent keys
  • Apps MCP tools
Collaborate
  • Comments and mentions
  • Approvals and versions
  • Prototypes
  • Design memory
Imports and integrations
  • Imports
  • Linear
  • Slack
  • Outbound webhooks
Teams and billing
Connect MCP

Other clients

Cline, Zed, LM Studio, n8n, stdio-only clients, and anything else that speaks MCP.

Any MCP client that supports remote servers over Streamable HTTP can use Floo. You need three things:

SettingValue
Addresshttps://worker.floo.design/mcp (or https://worker.floo.design/mcp/apps for the Apps library only)
TransportStreamable HTTP (http), not SSE
AuthenticationOAuth, or the header Authorization: Bearer cvk_… with an agent key

Cline

In Cline, open MCP Servers → Remote Servers, or edit cline_mcp_settings.json:

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

Zed

Add Floo to context_servers in Zed's settings.json. Zed signs in through the browser when it supports it; otherwise add the agent key header.

{
  "context_servers": {
    "floo": {
      "url": "https://worker.floo.design/mcp",
      "headers": {
        "Authorization": "Bearer cvk_your_agent_key"
      }
    }
  }
}

LM Studio and other mcp.json clients

LM Studio (Program → Install → Edit mcp.json) and many other clients read the common mcpServers format:

{
  "mcpServers": {
    "floo": {
      "url": "https://worker.floo.design/mcp",
      "headers": {
        "Authorization": "Bearer cvk_your_agent_key"
      }
    }
  }
}

n8n

Add an MCP Client Tool node to your AI Agent:

  1. Endpoint: the server address below.
  2. Server Transport: HTTP Streamable.
  3. Authentication: Bearer Auth, with an agent key as the token.
https://worker.floo.design/mcp

Clients that only run local (stdio) servers

Bridge them with mcp-remote: it runs locally, signs in to Floo through your browser, and forwards everything to the remote server. It needs Node.js 20 or newer.

{
  "mcpServers": {
    "floo": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://worker.floo.design/mcp"]
    }
  }
}

With an agent key instead of the browser sign-in:

{
  "mcpServers": {
    "floo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://worker.floo.design/mcp",
        "--header",
        "Authorization:${FLOO_AUTH}"
      ],
      "env": {
        "FLOO_AUTH": "Bearer cvk_your_agent_key"
      }
    }
  }
}

Test the connection

Any HTTP client can call the server directly. This lists the tools the key gives you:

curl -s https://worker.floo.design/mcp \
  -H "Authorization: Bearer $FLOO_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
PreviousGemini CLINextAgent keys