Skip to main content

Builder MCP

Not available yet

The Builder is in development. This page describes what it is for, so you can tell whether it covers your case — the setup details will land here when it ships. The Runner is available today.

Where the Runner executes workflows you already have, the Builder creates them. You describe what you want in plain language, the assistant assembles the workflow, validates it, and saves it to your account — then you open it in AI-Flow and keep working on it.

What it is for​

The visual editor is the right tool when you know the shape of what you are building. The Builder is for the step before that: turning "summarize incoming PDFs and post the result to Slack" into a real graph, with the right nodes wired together, that you can then refine by hand.

It is a starting point, not a replacement. Everything it produces is an ordinary workflow — nothing is locked, nothing is generated in a format you cannot edit.

What it will do​

  • Discover nodes. Search the catalog by intent rather than by name, so you do not have to know that the thing you want is called a Web Extractor.
  • Assemble and connect. Add nodes, wire outputs to inputs, set field values, and lay the graph out readably.
  • Validate before saving. Catch disconnected inputs, cycles and type mismatches while building, rather than at the first run.
  • Save to your account and hand you a link to open it in the editor.
  • Make flows automation-ready. When you intend to call a flow from outside AI-Flow, add the api-input / api-output nodes so it is API-compatible from the start — which is exactly what the Runner needs.
  • Reuse subflows so a piece of logic can be built once and dropped into several workflows.

What it will not do​

  • Publish templates. Template authoring stays an internal pipeline.
  • Run anything. Building and running are deliberately separate: the Builder cannot spend your credits. When you want to execute what you built, that is the Runner.

Credits and access​

Building and saving are free, and there is no tier requirement — it matches what you can already do for free in the editor. Only running a workflow costs credits and requires tier 3.

In the meantime​

You can already describe a workflow in natural language inside AI-Flow itself — see Getting started. The Builder brings that capability into your assistant, alongside the Runner, so building and running live in the same conversation.