mcp-flowise
The mcp-flowise server connects MCP clients (Claude, Cursor, etc.) to a local Flowise instance, exposing chatflows as callable tools.
list_chatflows()– Retrieve all available chatflows (id + name), filterable via whitelist/blacklist rules by ID or name regex.create_prediction(chatflow_id, question)– Execute a specific chatflow with a user question and return its response.trigger_webhook(chatflow_id, payload)– Trigger webhook-based chatflows with a custom JSON payload.Dynamic mode (
FLOWISE_DYNAMIC=true) – Automatically registers one tool per chatflow at startup (e.g.,flowise_support_bot(question)), enabling direct invocation by name.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-flowiselist available chatflows"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-flowise
MCP server that exposes the chatflows of your local Flowise as tools for Claude, Cursor, free-code, or any MCP client.
Tools
Simple mode (default):
list_chatflows()— lists available chatflows (id+name).create_prediction(chatflow_id, question)— runs a Chat/Form-trigger chatflow and returns its response.trigger_webhook(chatflow_id, payload)— runs a Webhook-trigger chatflow viaPOST /api/v1/webhook/{id}.
Dynamic mode (FLOWISE_DYNAMIC=true):
Registers one tool per chatflow at startup, e.g.
flowise_support_bot(question).
Related MCP server: OpenAPI MCP Server
Requirements
Installation
One-command install (any client)
npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client claude
npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client cursor
npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client free-code
npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client vscode
npx -y -p @suamkf08/mcp-flowise mcp-flowise-install --client windsurf-p @suamkf08/mcp-flowise pulls the published package that ships the
mcp-flowise-install binary; npx then runs that binary. (There is no separate
@suamkf08/mcp-flowise-install package on npm — the installer lives inside
@suamkf08/mcp-flowise.)
The script asks for your FLOWISE_API_ENDPOINT and FLOWISE_API_KEY, writes the config automatically, and tells you where it was saved. Restart your client after running it.
Manual install
Claude Desktop
Add this to your claude_desktop_config.json
(~/Library/Application Support/Claude/claude_desktop_config.json on macOS,
%APPDATA%\Claude\claude_desktop_config.json on Windows):
Option A — via npm (Node.js required):
{
"mcpServers": {
"mcp-flowise": {
"command": "npx",
"args": ["-y", "@suamkf08/mcp-flowise"],
"env": {
"FLOWISE_API_ENDPOINT": "http://localhost:3000",
"FLOWISE_API_KEY": ""
}
}
}
}Option B — via uvx (uv required):
Install uv first if you don't have it:
# macOS / Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"Then add to claude_desktop_config.json:
{
"mcpServers": {
"mcp-flowise": {
"command": "uvx",
"args": ["mcp-flowise"],
"env": {
"FLOWISE_API_ENDPOINT": "http://localhost:3000",
"FLOWISE_API_KEY": ""
}
}
}
}Cursor
Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):
{
"mcpServers": {
"mcp-flowise": {
"command": "npx",
"args": ["-y", "@suamkf08/mcp-flowise"],
"env": {
"FLOWISE_API_ENDPOINT": "http://localhost:3000",
"FLOWISE_API_KEY": ""
}
}
}
}free-code
Add to ~/.free-code/agent/mcp.json (or import with /mcp-import):
{
"mcpServers": {
"mcp-flowise": {
"command": "npx",
"args": ["-y", "@suamkf08/mcp-flowise"],
"env": {
"FLOWISE_API_ENDPOINT": "http://localhost:3000",
"FLOWISE_API_KEY": ""
}
}
}
}Then enable it in free-code:
/mcp enable mcp-flowise
/reloadConfiguration
Environment variable | Default | Description |
|
| Base URL of your Flowise instance |
| (empty) | Bearer token (Flowise → Settings → API Keys) |
|
| Set to |
| (empty) | Comma-separated chatflow IDs to include |
| (empty) | Comma-separated chatflow IDs to exclude |
| (empty) | Only include chatflows whose name matches |
| (empty) | Exclude chatflows whose name matches |
Development
git clone https://github.com/suamkf08/mcp-flowise
cd mcp-flowise
uv run mcp-flowise # starts over stdio; Ctrl+C to quitInspect with MCP Inspector:
uv run mcp dev mcp_flowise/server.pyFlowise API reference
List chatflows:
GET {endpoint}/api/v1/chatflowsRun chatflow:
POST {endpoint}/api/v1/prediction/{chatflowId}with{"question": "..."}Auth header:
Authorization: Bearer <FLOWISE_API_KEY>
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EnmaSuamkf/mcp-flowise'
If you have feedback or need assistance with the MCP directory API, please join our Discord server