The flo2 API
api.flo2.io is where your own agent — Claude Code or Grok Build, on your machine — connects to your flo2 designs. This page says what it is, how it differs from the flo2 connector you add in a chat app, and how to use it. The step-by-step guide walks through the setup.
What it is
An MCP server. MCP, the Model Context Protocol, is how an agent finds and calls tools; the API speaks it over HTTP rather than as a REST API, so there is no OpenAPI file to read. Your agent asks the server what it offers when it connects, and calls those tools by name.
Through it your agent gets reflow2's design toolkit on one of your designs — its own tools and skills, called directly. Every change is saved to the design on flo2.io, recorded as yours, and seen by anyone you share the design with.
Your files stay on your machine: flo2 never opens them. Tools that register files or check them for drift take what your agent measured and sent.
The API or the flo2 connector
Both reach the same designs under the same flo2 account, and a change from either lands in the same place, credited to you. They are for different places:
| The flo2 connector | The API | |
|---|---|---|
| Used from | A chat app: claude.ai, grok.com, chatgpt.com or gemini.google.com | Your own agent, on your machine: Claude Code or Grok Build |
| Address | https://flo2.io/mcp, one for all your designs |
https://api.flo2.io/mcp for your account, and one per design: https://api.flo2.io/g/its-id/mcp |
| What it offers | A few plain-language tools. The chat model reaches a design's tools and skills through them. | reflow2's own tools and skills on that design, called directly — among them the ones that take evidence from the files on your machine. |
| Signing in | Your flo2 account, from the chat app's connector settings | Your flo2 account in the browser (Claude Code), or your personal key (Grok Build) |
| Set it up | Connect your chat app | Below, and in the step-by-step guide |
Your account's address, once
https://api.flo2.io/mcp lists your designs and starts new ones. Add it once and it works
in every folder. Then ask your agent Using flo2, list my designs.
Each design's address
Each design has its own, https://api.flo2.io/g/its-id/mcp. You'll find it on the
design's page: open the design from Your designs and choose
Connect via the API, under its name. The commands there are already filled in for that design.
Run them in the project's folder. They add the design at project scope, so every session you start in that folder works on it, and anyone who clones the project gets the same connection. Add only the designs you are working on: each brings its full set of tools into the session.
Signing in, or a personal key
Claude Code signs in through your browser and needs no key: start claude, type
/mcp, choose the server, and sign in with your flo2 account. It can use a key instead
if you prefer.
Grok Build uses your personal key: its browser sign-in doesn't work with flo2 yet. Keep the key
in an environment variable named FLO2_API_KEY. The commands name the variable, in single
quotes, never the key itself, and your tool reads the key from your environment each time it
connects. Or Grok Build can skip all of this and use the flo2 connector on your grok.com account; the
guide says how.
A key works only here. Pasted into a chat app's connector, it opens nothing.
Your personal key
Never required: it's for a tool that won't open the browser sign-in. The same key, with the same controls, is under Connect via the API on each design's page. How to use it.
Sign in with your flo2 account to create, reset or revoke your key.
What an agent can call
Through a design's address, flo2.io serves reflow2 's skills and tools.
Your agent can list them itself (the tools when it connects, the skills with list_skills);
this is the same list, as flo2.io serves it today.
A person runs a skill by its shortcut, such as /where; the agent follows it, calling
the tools it names.
Skills
Tools
Retired tools
Your agent still sees these when it connects, marked retired. Calling one changes nothing: the answer names the tool that does its job now, if there is one. reflow2 counts each call, and a retired tool someone still needs is brought back.
A few tools that would open a file or another design on flo2's own disk are not served here. If your agent asks for one, it is told why.