Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

A Model Context Protocol server that enables LLM tools to create, manage, and run Flowise chatflows and agentflows programmatically.

README.md

Flowise MCP Server

A Model Context Protocol (MCP) server that provides programmatic integration with Flowise AI workflow platform. This enables LLM-based tools like Claude Code to create, manage, and run Flowise chatflows and agentflows.

Features

  • Run Predictions: Execute chatflows with questions, conversation history, file uploads, or lead capture
  • Manage Chatflows: Create, update, delete, and list chatflows programmatically
  • Node Discovery: List all available nodes and get detailed specifications for building flows
  • Full Flow Types: Supports CHATFLOW, AGENTFLOW, MULTIAGENT, and ASSISTANT types

Prerequisites

Installation

# Clone the repository
git clone https://github.com/wksbx/flowise-mcp-server.git
cd flowise-mcp-server

# Install dependencies
pnpm install

# Build the project
pnpm build

Configuration

  1. Copy the example environment file:
cp .env.example .env
  1. Edit .env with your Flowise settings:
FLOWISE_BASE_URL=http://localhost:3000
FLOWISE_API_KEY=your-api-key-here
  • FLOWISE_BASE_URL: URL where your Flowise instance is running
  • FLOWISE_API_KEY: API key from Flowise (Settings > API Keys)

Usage

Running Directly

pnpm start

Running with Docker

# Build the Docker image
pnpm docker:build

# Run the container
pnpm docker:run

Configuring with MCP Clients

Add to your MCP client configuration (e.g., Claude Desktop, Claude Code):

Using Node directly:

{
  "mcpServers": {
    "flowise": {
      "command": "node",
      "args": ["/path/to/flowise-mcp-server/dist/index.js"],
      "env": {
        "FLOWISE_BASE_URL": "http://localhost:3000",
        "FLOWISE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Using Docker:

{
  "mcpServers": {
    "flowise": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "--add-host=host.docker.internal:host-gateway",
        "--env-file", "/path/to/your/.env",
        "flowise-mcp-server"
      ]
    }
  }
}

Available Tools

Prediction Tools

| Tool | Description | |------|-------------| | create_prediction | Run a chatflow with a question | | create_prediction_with_history | Run with conversation history for context | | create_prediction_with_files | Run with file attachments (images, documents) | | create_prediction_with_lead | Run and capture lead email |

Chatflow Management

| Tool | Description | |------|-------------| | list_chatflows | List all available chatflows | | get_chatflow | Get a specific chatflow's configuration | | create_chatflow | Create a new chatflow | | update_chatflow | Update an existing chatflow | | delete_chatflow | Delete a chatflow (irreversible) |

Node Discovery

| Tool | Description | |------|-------------| | list_nodes | List all available node types | | get_nodes_by_category | Get nodes filtered by category | | get_node | Get detailed spec for a specific node type |

Examples

Running a Chatflow

Use create_prediction with:
- chatflowId: "abc123"
- question: "What is the weather today?"

Creating a Simple Chatflow

1. Use get_node to fetch specs for needed nodes (e.g., "chatOpenAI", "llmChain")
2. Use create_chatflow with:
   - name: "My Chatflow"
   - flowData: { nodes: [...], edges: [...] }
   - type: "CHATFLOW"

Development

# Build TypeScript
pnpm build

# Run in development mode (build + run)
pnpm dev

Testing

The project includes comprehensive unit tests using Vitest.

# Run tests once
pnpm test

# Run tests in watch mode
pnpm test:watch

# Run tests with coverage report
pnpm test:coverage

Test Structure

src/
├── flowise-api.test.ts   # API client tests (8 tests)
└── handlers.test.ts      # Tool handler tests (26 tests)

Project Structure

flowise-mcp-server/
├── src/
│   ├── index.ts           # MCP server entry point
│   ├── flowise-api.ts     # Flowise API client
│   ├── handlers.ts        # Tool handler functions
│   └── *.test.ts          # Unit tests
├── dist/                  # Compiled JavaScript (generated)
├── package.json
├── tsconfig.json
├── vitest.config.ts       # Test configuration
├── Dockerfile
├── .env.example           # Environment template
└── mcp-config.example.json

Troubleshooting

Connection Issues

  • Ensure Flowise is running and accessible at the configured URL
  • When using Docker, use host.docker.internal to connect to Flowise on the host machine
  • Verify your API key is correct in Flowise settings

Authentication Errors

  • Check that your FLOWISE_API_KEY matches one configured in Flowise
  • API keys can be created in Flowise under Settings > API Keys

License

MIT - see LICENSE

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Related Projects

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use AI & ML servers.