Flow-Like MCP
Flow-Like
Flow-Like MCP nodes expose visual workflow functions to an agent over HTTP, with owner-selected tools and access
- 972 ★ on the repository
- Last commit
Extended access
Why this level
- MCP invokes the chosen functions of your workflow with their file and service permissions.
- Network misconfiguration can expose these functions to others; node credentials can permit data changes and external API usage.
Install
- Works in
Manual install
Check Studio installation and create a local test flow. Use `MCP Server Config`, register one function and pass the configuration to `MCP Server`. Keep the `127.0.0.1` binding. Read `Local Addr`, append the configured `/mcp` path and prepare the client’s HTTP connection. Show function arguments and permissions before calling it.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- MCP invokes the chosen functions of your workflow with their file and service permissions.
- Network misconfiguration can expose these functions to others; node credentials can permit data changes and external API usage.
This is third-party code. Review the repository files before installing.
What it does
Flow-Like can assemble an MCP server from visual workflow functions. In the editor, configure the server and register selected functions, then start the `MCP Server` node. An agent receives those functions as HTTP tools. The configuration can also include resources and prompts. Flow-Like builds tool schemas from the selected functions’ parameters. Names and descriptions help the agent choose calls; one server combines several workflow functions. An MCP call runs a function in Flow-Like. Its nodes determine file, network and credential access. Studio is suitable for a local prototype. A shared backend needs separate infrastructure and user configuration.
Who it is for. For developers exposing existing Flow-Like workflows to a coding agent.
Good fit when
- An existing visual workflow needs calls from an MCP client
- You want to expose selected functions rather than the whole application
- Tool schemas should come from workflow function parameters
- You want to test a local MCP server before shared deployment
Not a fit when
- You need one ready-made tool without a visual workflow environment
- Your company falls outside the BSL use grant and cannot arrange a commercial license
- The client supports only stdio, with no HTTP connection or external bridge available
Example request
Help expose one test Flow-Like function through local MCP. Show the address and tool list; leave file-writing functions out for now.MCP
- Transport
- http
- Authentication
- not required
Limitations
Install Studio and build a flow with MCP nodes; it does not supply ready-made functions for your service. A first local flow needs no account or model, but AI nodes and external services need their own keys and payment. BSL 1.1 restricts competing products; organizations above 2,000 employees or 300 million euros in annual revenue need a commercial license. Prepare a shared server separately on Linux with Docker and gVisor; Studio installation alone is insufficient.
How to disable. Stop the running flow containing `MCP Server` and remove its HTTP connection from the agent. Preserve the project before removing Studio or backend data. Revoke external-service keys used by its workflow functions when appropriate.
FAQ
What do I install for a local MCP server?
Install Flow-Like Studio from `https://flow-like.com/download` and create a local project. The workflow’s `MCP Server` node starts the server.
How do I find the connection address?
`MCP Server` returns the bound socket address in `Local Addr`. For local HTTP, prefix it with `http://` and append the configured path, `/mcp` by default. With port 0, the address may change after a restart.
Can the server require authentication?
Yes, through `Register MCP Auth`. Flow-Like user verification through OAuth applies to hosted public servers; it is not an automatic protection for the local variant.
Will every workflow function be available?
No. Register only the functions you want to expose in the configuration. Inspect the actual tool list after changes.
Does the first test need a cloud account?
No. Studio can run a simple function in a local project without a model. Credentials are needed when the function itself calls external services.
What is the local MCP address?
It defaults to 127.0.0.1 and /mcp. Port 0 lets the OS select a free port; connect to the actual address shown in Local Addr.
Discussion
No questions or reviews yet.
Related
MCP serversThe MCP server of the Loonflow platform: an agent reads the ticket and approval queue and acts on tickets
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
MCP server and wincli CLI: agents drive Windows apps by control name through UI Automation instead of screen coordinates
An open-core platform: workflows and actions of connected services are published as MCP tools for Claude, Cursor and Windsurf
An MCP server for macOS: the agent moves the mouse, types, manages windows and captures the screen when an app has no API
apra-fleet runs a fleet of AI agents across machines and models through MCP and drives multi-hour workflows
README in short
`Timeout Seconds` limits the server’s lifetime. Setting it to 0 disables that timeout, leaving the server running until cancelled.