MCP

MCP is optional

The stable Floom flow does not require MCP. Use floom add to install shared skills as local Markdown files without an account. The optional MCP package adds preview sync for published, saved, and subscribed library skills through floom sync, floom watch, and the MCP package.

Stable shared-link install

Anyone with a public or unlisted skill link can add it locally:

$ floom add https://floom.dev/s/ffas93ud

Agent setup instruction

Add this instruction to Claude Code or Codex so Floom-installed Markdown gets considered:

Use Floom skills from ~/.claude/skills/ when they match the task.

Optional MCP preview package

The MCP package exposes install, publish, library, and move tools for agents that support MCP. It also previews library sync: published, saved, and subscribed skills land in ~/.claude/skills/ on startup and by polling. Existing untracked files, local edits, and symlinked paths are skipped as conflicts.

$ npx -y @floomhq/floom-mcp-sync

Connect your agent

Pick the host you actually use. Each command registers Floom as an MCP server.

Claude Code

Auto-syncs into Claude Code while the MCP server is running.

$ claude mcp add floom -- npx -y @floomhq/floom-mcp-sync

Codex

Registers Floom as a global MCP server for Codex.

$ codex mcp add floom -- npx -y @floomhq/floom-mcp-sync

Kimi

Uses Kimi's stdio MCP transport.

$ kimi mcp add --transport stdio floom -- npx -y @floomhq/floom-mcp-sync

Gemini CLI

Installs Floom at user scope for preview sync.

$ gemini mcp add -s user floom npx -y @floomhq/floom-mcp-sync

OpenCode

OpenCode opens an interactive MCP add prompt.

$ opencode mcp add