list_chatflowsLABSCO SUMMARY
Pick the mode before you pick anything else.
LowLevel mode is the interesting one: your chatflows arrive as distinct tools with distinct descriptions, so the agent routes to the right flow instead of you naming it every time. That only works if the descriptions are good, which is what the descriptions variable is for — leave it empty and the agent is choosing between chatflow names. Simple mode is the right call when there is one flow that matters. Whitelists take precedence over blacklists when both are set.
What it is
A Python MCP server that connects to a Flowise instance and exposes your chatflows to an MCP client. It runs in one of two modes, and the choice matters: LowLevel mode registers every chatflow as its own separate tool, so an agent can pick between them; FastMCP mode exposes two static tools instead, which is less to configure and less for the model to reason about.
What you get
- Every chatflow on your Flowise instance registered as an individual tool, named after the chatflow and described from
FLOWISE_CHATFLOW_DESCRIPTIONS, so the agent chooses which flow fits the question — the default LowLevel mode - Or, with
FLOWISE_SIMPLE_MODE=true, two tools instead of many: one to list the chatflows and one to run a prediction against a configured chatflow or assistant —list_chatflows,create_prediction - Filtering in either mode, so a busy Flowise instance does not dump everything into your client: whitelist or blacklist by chatflow ID, or by name with a regular expression —
FLOWISE_WHITELIST_ID,FLOWISE_BLACKLIST_ID,FLOWISE_WHITELIST_NAME_REGEX,FLOWISE_BLACKLIST_NAME_REGEX - A documented Windows path that avoids the
--from git+httpsproblem: clone locally and pointuvx.exeat the directory
Requirements
A Flowise instance and its API bearer token: FLOWISE_API_KEY is required, FLOWISE_API_ENDPOINT defaults to http://localhost:3010. Python 3.12 or higher and the uvx package manager; run straight from the repository with uvx --from git+https://github.com/andydukes/mcp-flowise mcp-flowise, or install through Smithery for Claude Desktop. The package is mcp-flowise (version 0.1.0). Setting both FLOWISE_CHATFLOW_ID and FLOWISE_ASSISTANT_ID makes the server refuse to start — pick one.
Setup effort
One command plus a key — uvx --from git+https://github.com/andydukes/mcp-flowise mcp-flowise, then supply credentials
USE CASES
01
Letting an agent choose between your flows
Run the default mode with descriptions filled in, so each chatflow arrives as its own tool the agent can route to.
02
Exposing a single flow with minimum setup
Switch on simple mode, set the chatflow ID, and get one prediction tool instead of a dynamic tool list.
03
Keeping a crowded Flowise instance out of your client
Filter by ID, or by a name pattern, so only the flows meant for this client show up.
04
Finding out what is on the instance
List the chatflows to see the IDs and names before writing any filter or picking a default.
2 tools
Listed in project docs. Your client may show a different list.
create_predictionBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- uvx on PATH
- Python 3.12 or later
- FLOWISE_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx --from git+https://github.com/andydukes/mcp-flowise mcp-flowiseMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-flowise": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/andydukes/mcp-flowise",
"mcp-flowise"
],
"env": {
"FLOWISE_API_KEY": "<YOUR_FLOWISE_API_KEY>",
"FLOWISE_API_ENDPOINT": "<YOUR_FLOWISE_API_ENDPOINT>"
}
}
}
}Claude Desktop — Windows
CLAUDE DESKTOP — WINDOWS · JSON
{
"mcpServers": {
"flowise": {
"command": "C:\\Users\\matth\\.local\\bin\\uvx.exe",
"args": [
"--from",
"C:\\Users\\matth\\downloads\\mcp-flowise",
"mcp-flowise"
],
"env": {
"LOGLEVEL": "ERROR",
"APPDATA": "C:\\Users\\matth\\AppData\\Roaming",
"FLOWISE_API_KEY": "<YOUR_FLOWISE_API_KEY>",
"FLOWISE_API_ENDPOINT": "http://localhost:3010/"
}
}
}
}The C:\\Users\\matth paths in this block are from the README author's machine, not yours: put in the full path to your own uvx.exe, to your own clone of this repository (git clone https://github.com/andydukes/mcp-flowise), and to your own AppData\\Roaming folder, and your own Flowise API key and base URL in the two FLOWISE_ values.
