Skip to content
Sub Flows logo

Sub Flows MCP server

Trigger and call another sub flow.

Sub Flows is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
3
Works with
Any MCP client
License
MIT, open source
Updated
August 2026

About the Sub Flows MCP server

Connect Sub Flows once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Sub Flows and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Sub Flows tools your AI can run

Once connected, your assistant can call any of these Sub Flows actions by asking in plain language.

  • Call Flow

    Call a flow that has "Callable Flow" trigger

    4 fields

  • Stream CSV to Subflows

    Stream a CSV and call a subflow once per batch of rows, without loading the whole file into memory.

    5 fields

  • Return Response

    Return response to the original flow

    2 fields

Triggers

Sub Flows events your agent can watch

These start a run the moment something happens in Sub Flows, so work gets picked up on its own.

  • Callable Flow

    Waiting to be triggered from another flow

    2 fields

Give your assistant Sub Flows

Connect Sub Flows once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Sub Flows MCP, answered.

No. That is the point of it. One Activepieces server exposes Sub Flows alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Sub Flows in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 3 tools, including Call Flow, Stream CSV to Subflows, Return Response, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.