AI assistants
Let an assistant such as Claude build, check and dial your flows through MCP.
Luftflow speaks MCP, the protocol AI assistants use to reach other tools. Connected, an assistant can build, check and dial the flows in your organization for you, through the same path the editor itself saves through.
Connect one
- Open Settings → API tokens and make an API token. It is shown once, so copy it then.
- In the connector section of the same tab, copy the server address and the settings for your assistant. The token goes in as a bearer credential.
- Add them to your assistant: in Claude Code or Cursor, the
mcpServersconfig it reads; in claude.ai, a custom connector with an authorization header.
What it can do
A token acts as you, in one organization, at your own role there. An assistant connected as an editor can change flows and publish versions, and like you it cannot put a version live unless you are an admin.
Revoke a token on that tab to cut an assistant off at once.
Working with it
Ask for outcomes, not YAML: "Add a menu after the PIN screen that lists the customer's accounts from /accounts, with a Back option." The assistant reads the flow, makes the change, runs the checks, and can dial the flow to confirm the path works. Changes it makes appear in your open editor like a teammate's.