One connector for the assistants, agent platforms and developer tools your team already talks to. It reads the same flows and brainstorms and can move the work, as the person who connected it, under their own role. No separate account, no key to manage.
✦ Included with Pro · No per-call pricing · OAuth 2.1 + PKCE, in a browser
You: What's blocking the Acme launch?
work_blocked()
→ "Schedule & go live" blocked
needs: Client approval (ready · with client)
item_comment("Client approval",
"Following up, can we get sign-off today?")
→ noted, visible in the activity feed
work_available()
→ "Client approval" (ready)
assigned to: ClientConnect Flowral to an AI assistant, work platform or developer tool. You will sign in and review access before anything is enabled.
Ask about projects, create tasks and move work forward in conversation.
Bring Flowral projects into the agent platform your organisation manages.
Use Flowral project context while planning, coding and shipping. Coding in an agent like Claude Code or Cursor? See how to set it real targets and let it execute on them →
A native extension, not just an MCP install: My Work, Available and In Progress as sidebar trees, a status bar count that updates the moment something unblocks, and the flow's dependency graph in a panel beside your code. Start, complete, reopen and comment without switching windows.
Included with Pro, the same plan as the REST API and MCP connector. It only starts, completes or reopens work assigned to you or unassigned, never someone else's.
Use Flowral tools inside workflows and custom agents.
https://mcp.flowral.app
The connector signs the person in through Flowral's own login (Google, Microsoft, WIINK or a password) and keeps the session it gets back. There is no second account and no key to distribute: revoking the connection ends a session the app already understands. What it may do is a list of scopes shown on the consent screen, and what it can do is whatever that person's role allows, which the API enforces either way.
One thing to weigh with your own head: whatever your assistant asks Flowral for, the company that makes it also holds, under their terms. That's a per-workspace decision, not a switch we should flip for you.
€9 per person per month, everything included: templates, dates, reports, the connector and the REST API. No add-on fee, no per-call pricing, no credits to buy.
Free gives you the whole canvas: unlimited flows, gates, the Ready view, unlimited guests, two people. What Pro adds is everything that involves accounting for the work rather than doing it, including programmatic and conversational access to the workspace. Building your own integration instead? See the REST API →
Pick it from the list above and follow the guided setup, or paste the Flowral MCP URL into any MCP-capable client yourself. You sign in and review access before anything is enabled.
No. It signs in through Flowral's own login as the person who connected it, and acts under that person's role, just as if they had made the change themselves.
Use MCP when you want Flowral available inside an AI assistant, enterprise agent, developer tool or automation platform. Use the REST API for software and automated workflows you build and host yourself.
Yes. Flowral for VS Code adds My Work, Available and In Progress as sidebar trees, a status bar count that updates when work unblocks, and a read-only dependency graph, so you can see and act on your work without leaving the editor. It's on the VS Code Marketplace and included with Pro.
It's included with Pro at €9 per person per month, the same plan as the REST API and webhooks. There is no separate connector fee.
Running an autonomous agent instead of chatting? See how targets and execution work.
See AI agent targets →