Chatting with FlowArray from Claude
Connect FlowArray as a tool server and Claude can list, inspect, create and run your flows in conversation — and anything it creates is a draft that cannot spend.
In this article (4)
FlowArray is itself an MCP server, so an assistant can work with your flows directly: "run the listing pack over these twelve SKUs", "what did last night's digest produce?"
Connect it (no tokens to copy)
In Claude Code:
claude mcp add flowarray https://flowarray.app/api/mcp -t http
then /mcp → Connect. A browser opens, you sign in with your FlowArray account (email or Google), and you are connected. Signing in is the consent step; access is renewed automatically afterwards.
For headless or back-end callers that cannot open a browser, mint a bearer token under Settings → MCP access and pass it as Authorization: Bearer <token> — see the API.
What Claude can then do
List and inspect your workflows, create new ones, run them (up to 20 items per call), and read results.
The two limits that make this safe
- Chat-created flows arrive as drafts in free test mode — no pools attached, so they produce placeholder output until a person opens them in the Builder and points them at real keys. Chatting can never spend money on its own.
- Access acts as you, with your role, and everything still obeys the workspace's daily spend limit. Revoking a token or a connection cuts access immediately.
Where to look when something is off
Runs started this way appear in Runs like any other, and Settings → MCP access lists what has access so you can revoke it.