Flowise MCP server

Integrates Flowise chatflows and assistants with MCP, enabling seamless incorporation of AI-powered conversational interfaces into existing systems.
Back to servers
Provider
Matthew Hand
Release date
Jan 09, 2025
Language
Python
Stats
23 stars

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.

Installation

Via Smithery for Claude Desktop

npx -y @smithery/cli install @matthewhand/mcp-flowise --client claude

Prerequisites

  • Python 3.12 or higher
  • uvx package manager

Run Directly Using uvx

uvx --from git+https://github.com/matthewhand/mcp-flowise mcp-flowise

Integrate with MCP Ecosystem

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}"
            }
        }
    }
}

Operation Modes

FastMCP Mode (Simple Mode)

Enable by setting FLOWISE_SIMPLE_MODE=true. This mode:

  • Exposes two tools: list_chatflows and create_prediction
  • Allows static configuration using FLOWISE_CHATFLOW_ID or FLOWISE_ASSISTANT_ID
  • Lists all available chatflows via list_chatflows

LowLevel Mode (Default)

When FLOWISE_SIMPLE_MODE=false or not set:

  • Dynamically registers all chatflows as separate tools
  • Tools are named after normalized chatflow names
  • Uses descriptions from FLOWISE_CHATFLOW_DESCRIPTIONS or falls back to chatflow names

Windows Setup

If using Windows and encountering issues with --from git+https:

  1. Clone the repository locally
  2. Configure 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/"
      }
    }
  }
}

Environment Variables

Required Configuration

  • FLOWISE_API_KEY: Your Flowise API Bearer token (required)
  • FLOWISE_API_ENDPOINT: Base URL for Flowise (default: http://localhost:3000)

LowLevel Mode Configuration

  • FLOWISE_CHATFLOW_DESCRIPTIONS: Comma-separated list of chatflow_id:description pairs
    FLOWISE_CHATFLOW_DESCRIPTIONS="abc123:Chatflow One,xyz789:Chatflow Two"
    

FastMCP Mode Configuration

  • FLOWISE_CHATFLOW_ID: Single Chatflow ID (optional)
  • FLOWISE_ASSISTANT_ID: Single Assistant ID (optional)
  • FLOWISE_CHATFLOW_DESCRIPTION: Optional description for the single tool exposed

Filtering Chatflows

Apply filters using these environment variables:

  • Whitelist by ID:
    FLOWISE_WHITELIST_ID="id1,id2,id3"
  • Blacklist by ID:
    FLOWISE_BLACKLIST_ID="id4,id5"
  • Whitelist by Name (Regex):
    FLOWISE_WHITELIST_NAME_REGEX=".*important.*"
  • Blacklist by Name (Regex):
    FLOWISE_BLACKLIST_NAME_REGEX=".*deprecated.*"

Note: Whitelists take precedence over blacklists.

Troubleshooting

  • Missing API Key: Ensure FLOWISE_API_KEY is set correctly
  • Invalid Configuration: The server won't start if both FLOWISE_CHATFLOW_ID and FLOWISE_ASSISTANT_ID are set
  • Connection Errors: Verify FLOWISE_API_ENDPOINT is reachable

How to add this MCP server to Cursor

There 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.

Adding an MCP server to Cursor globally

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"
            ]
        }
    }
}

Adding an MCP server to a project

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.

How to use the MCP server

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.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later