MCP server

Overview

Floom is a Model Context Protocol (MCP) server. Point any MCP client — Claude Code, Cursor, Codex, Windsurf, Continue — at Floom and your assistant can run workers, read runs, edit the company brain, manage connections, and resolve approvals, all scoped to one workspace.

The server exposes 58 tools across 11 categories. Most tools wrap a REST endpoint, so the MCP surface stays close to the REST API. Secrets and tokens are automatically redacted from tool results.

Connect a client

The CLI writes the right config for your client. Install it once, then add Floom:

Run floom login --cloud first so the server has a token. For clients that take a raw URL, point them at your workspace endpoint with a token header (see below). Verify any time with floom mcp test.

Transport & auth

Floom Cloud serves MCP over HTTP JSON-RPC at a per-workspace endpoint. Authenticate with a Bearer token — a personal/workspace API token is ideal because, unlike a session JWT, it does not expire and suits static client config.

{
  "mcpServers": {
    "floom": {
      "url": "https://workeros-api.floom.dev/mcp/<workspace_id>",
      "headers": { "Authorization": "Bearer <floom_token>" }
    }
  }
}

• Endpoint — POST https://workeros-api.floom.dev/mcp/{workspace_id}. The path’s workspace must match your token’s workspace.
• Auth — Authorization: Bearer <token> (API token recommended; Supabase JWT also accepted).
• Self-hosted — the OSS server runs over stdio (the floom-mcp binary) using x-floom-secret or x-floom-token.

Tool annotations

Each tool carries standard MCP hints so clients can render and gate it appropriately:

• readOnlyHint — the tool only reads (e.g. workers.list, runs.get).
• destructiveHint — the tool deletes or irreversibly changes state (e.g. workers.delete).
• idempotentHint — repeating the call with the same args is safe.
• openWorldHint — the tool reaches external systems (e.g. running a worker, testing a connection).

Tool reference

58 tools, grouped by category. Names are the registered tool names; some clients render dots as underscores when they namespace tools (e.g. workers.list → workers_list).