Skip to main content
floo’s MCP server is hosted at https://api.getfloo.com/mcp. It speaks Streamable HTTP and signs you in with OAuth, so there is no key to copy. Every tool calls the same /v1 API as the CLI, with your account’s permissions.

​
Claude Code

Install the floo plugin. It adds the MCP server and the floo skill together:
Or add only the server:
Run /mcp in Claude Code, pick floo, and approve the sign-in in your browser.

​
Claude (claude.ai and desktop)

In Settings → Connectors, choose Add custom connector, name it floo, and enter https://api.getfloo.com/mcp. Claude opens floo’s sign-in when you connect.

​
Codex

​
Cursor

Add to .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project:

​
VS Code

Add to .vscode/mcp.json:

​
Use an API key instead of OAuth

For CI or a headless agent, send a floo API key as a bearer token. Create one under API keys at app.getfloo.com/settings.

​
What the sign-in grants

Approving the sign-in creates an API key named MCP: <client name> with the highest scope your role allows. It appears under API keys at app.getfloo.com/settings; revoke it there to disconnect the client. Org roles and approval policies still apply to every call.

​
Tools

get_deploy waits up to 25 seconds per call when you pass wait. Call it again until the deploy is live or failed. For the full deploy loop, give your agent getfloo.com/agents.md. The MCP tools are the calls it names.