flo2

Use flo2 from Claude Code or Grok Build

If you work in a terminal with Claude Code or Grok Build, you can point it straight at your designs on flo2. Your agent gets the whole design toolkit — the same one a chat app reaches through flo2's connector, but all of it — and every change is saved to your design on flo2.io and credited to you. It works the same on macOS and Linux.

Using Claude, Grok, ChatGPT or Gemini in a browser instead? You want the chat app steps.

Before you start

Using Grok Build? You may already be connected

If you've connected flo2 in grok.com, Grok Build can use that connection: it works with the connectors on the grok.com account it's signed in with. Nothing to add, no key. To tie a project folder to one design, add a line to the project's AGENTS.md:

This project's design is on flo2: design ITS-ID. Pass it on every flo2 call.

Replace ITS-ID with the design's id, in its address under Connect via the API on the design's page in your designs, or ask Grok Using flo2, list my designs. This way reaches flo2 through its chat connector, which is plenty for designing. The steps below connect straight to api.flo2.io instead, for the full design toolkit.

1 Add your flo2 account, once

This address lists your designs and starts new ones. Add it once and it works in every folder.

Claude Code

claude mcp add --transport http --scope user flo2 https://api.flo2.io/mcp

Start claude, type /mcp, choose flo2 and sign in with your flo2 account in the browser window that opens.

Grok Build

grok mcp add --transport http flo2 https://api.flo2.io/mcp --header 'Authorization: Bearer ${FLO2_API_KEY}'

Grok Build connects to api.flo2.io with your personal key: create one on the API page and keep it in FLO2_API_KEY first. Its browser sign-in doesn't work with flo2 yet — Grok Build asks to register itself in a way flo2's sign-in service doesn't accept.

2 Start a design, or find one you have

Ask your agent, in your own words:

Either answer gives each design's own address, which looks like https://api.flo2.io/g/its-id/mcp. Each design's page in your designs has it too: choose Connect via the API, under the design's name, for its address with the commands for step 3 already filled in.

3 Add the design to your project folder

In a terminal, cd into the folder for the project, then add the design under a short name of your choosing — here greenhouse. The project scope saves it in that folder, so every session you start there works on that design. Commit the file it writes, and anyone who clones the project gets the same connection.

Claude Code writes .mcp.json

claude mcp add --transport http --scope project greenhouse https://api.flo2.io/g/ITS-ID/mcp

Grok Build writes .grok/config.toml

grok mcp add --transport http --scope project greenhouse https://api.flo2.io/g/ITS-ID/mcp --header 'Authorization: Bearer ${FLO2_API_KEY}'

Replace ITS-ID with the design's id, or copy the finished command from the design's page in your designs, under Connect via the API. Claude Code signs in the same way as in step 1 the first time; Grok Build uses your key.

4 Work on it

Start claude or grok in that folder and work as you normally would — /genesis to set up a new design, /where to see where it stands, /gaps for what's still undecided. Everything you change is saved on flo2.io, recorded as yours, and seen by anyone you share the design with.

Good to know

More than one design in a session

Add each one under its own name, the same way as step 3. Each design's tools are kept separate by that name, so a change can't land in the wrong design. Add only the ones you are working on: each brings its full set of tools into the session.

Check the connection

claude mcp list, or grok mcp list and grok mcp doctor greenhouse. To remove one: claude mcp remove greenhouse or grok mcp remove greenhouse.

Changes are refused, but reading works

The first time a new app signs in, flo2 may give it permission to read but not yet to change designs. Tell the person who invited you to flo2 which app you're using; they switch it on once, and it stays on.

Files on your machine

The design lives on flo2.io, but your files stay on your machine, and flo2 never opens them. Tools that register files, check them for drift or read a folder of documents work normally: your agent reads the files and sends flo2 what it found. Eight tools that open a file by path themselves, such as comparing against a saved copy of a design, are not offered here yet. A small reflow2 helper that runs on your machine and opens those files for them is on the way.

A personal key instead of signing in

Never required. It's for a tool that won't open the browser sign-in.

  1. Create your key on the API page, or under Connect via the API on any design's page. It is shown once: copy it then.
  2. Keep it in an environment variable named FLO2_API_KEY, for example in your shell's profile. Never paste the key itself into a command, a file you commit, or a chat.
  3. Add the design with the key's name in the header. The single quotes matter: they store ${FLO2_API_KEY} as written, and your tool reads the key from your environment each time it connects.

Claude Code, in the project's folder (it reads the variable from the project's .mcp.json):

claude mcp add --transport http --scope project greenhouse https://api.flo2.io/g/ITS-ID/mcp --header 'Authorization: Bearer ${FLO2_API_KEY}'

Grok Build:

grok mcp add --transport http --scope project greenhouse https://api.flo2.io/g/ITS-ID/mcp --header 'Authorization: Bearer ${FLO2_API_KEY}'

A key opens your designs on api.flo2.io and nothing else: it does not work in a chat app's connector. It lasts 90 days. It is one key for all your designs, so resetting it, whenever you like, stops the old one at once for every agent using it, on every design.

Only you can see your designs, and anyone you share one with sees only that one.