This MCP-Flowise server integrates with the Flowise API to provide a standardized way to interact with Flowise chatflows and assistants. It supports two operation modes: LowLevel Mode for dynamic tool registration and FastMCP Mode for simpler configurations.
npx -y @smithery/cli install @matthewhand/mcp-flowise --client claude
uvx
package manageruvx
uvx --from git+https://github.com/matthewhand/mcp-flowise mcp-flowise
Add the following to your mcpServers
configuration:
{
"mcpServers": {
"mcp-flowise": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/matthewhand/mcp-flowise",
"mcp-flowise"
],
"env": {
"FLOWISE_API_KEY": "${FLOWISE_API_KEY}",
"FLOWISE_API_ENDPOINT": "${FLOWISE_API_ENDPOINT}"
}
}
}
}
Enable by setting FLOWISE_SIMPLE_MODE=true
. This mode:
list_chatflows
and create_prediction
FLOWISE_CHATFLOW_ID
or FLOWISE_ASSISTANT_ID
list_chatflows
When FLOWISE_SIMPLE_MODE=false
or not set:
FLOWISE_CHATFLOW_DESCRIPTIONS
or falls back to chatflow namesIf using Windows and encountering issues with --from git+https
:
mcpServers
with full paths:{
"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-api-key-goes-here",
"FLOWISE_API_ENDPOINT": "http://localhost:3000/"
}
}
}
}
FLOWISE_API_KEY
: Your Flowise API Bearer token (required)FLOWISE_API_ENDPOINT
: Base URL for Flowise (default: http://localhost:3000
)FLOWISE_CHATFLOW_DESCRIPTIONS
: Comma-separated list of chatflow_id:description
pairs
FLOWISE_CHATFLOW_DESCRIPTIONS="abc123:Chatflow One,xyz789:Chatflow Two"
FLOWISE_CHATFLOW_ID
: Single Chatflow ID (optional)FLOWISE_ASSISTANT_ID
: Single Assistant ID (optional)FLOWISE_CHATFLOW_DESCRIPTION
: Optional description for the single tool exposedApply filters using these environment variables:
FLOWISE_WHITELIST_ID="id1,id2,id3"
FLOWISE_BLACKLIST_ID="id4,id5"
FLOWISE_WHITELIST_NAME_REGEX=".*important.*"
FLOWISE_BLACKLIST_NAME_REGEX=".*deprecated.*"
Note: Whitelists take precedence over blacklists.
FLOWISE_API_KEY
is set correctlyFLOWISE_CHATFLOW_ID
and FLOWISE_ASSISTANT_ID
are setFLOWISE_API_ENDPOINT
is reachableThere are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.