Flowise MCP Server
An MCP (Model Context Protocol) server that enables AI agents to interact with Flowise instances. Works with Claude Desktop, VS Code GitHub Copilot, Cursor, and other MCP-compatible clients.
Features
- Flow Management: List, create, update, and delete chatflows and agentflows
- Predictions: Send messages to flows and receive responses
- Flow Analysis: Analyze configurations with improvement suggestions
- Assistants: List and inspect Flowise assistants
- Document Stores: Manage document stores for RAG
- Vector Operations: Upsert vectors and query vector stores
- Chat History: Retrieve and delete conversation history
- Variables & Tools: Manage global variables and tools
Requirements
- Python 3.10+ or uv package manager
- A running Flowise instance with API access
Installation
Option A: Using pip
pip install flowise-mcp
Option B: Using uv (recommended)
# Install uv first if you don't have it
# Windows (PowerShell)
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
# macOS/Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
Then configure your AI client to use uvx flowise-mcp (see below).
Configuration
Environment Variables
| Variable | Description | Required |
|---|---|---|
FLOWISE_BASE_URL |
Your Flowise instance URL | Yes |
FLOWISE_API_KEY |
API key for authentication | Yes |
FLOWISE_TIMEOUT |
Request timeout in seconds (default: 60) | No |
Getting your Flowise API Key
- Open your Flowise instance
- Go to Settings > API Keys
- Create a new API key or copy an existing one
Setup by Client
VS Code (GitHub Copilot)
Requires VS Code 1.99+ with GitHub Copilot.
Add to .vscode/mcp.json in your project or to your User Settings (JSON):
{
"servers": {
"flowise": {
"command": "uvx",
"args": ["flowise-mcp"],
"env": {
"FLOWISE_BASE_URL": "https://your-flowise-instance.com",
"FLOWISE_API_KEY": "your-api-key"
}
}
}
}
Restart VS Code after adding the configuration.
Claude Desktop
Add to your config file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"flowise": {
"command": "uvx",
"args": ["flowise-mcp"],
"env": {
"FLOWISE_BASE_URL": "https://your-flowise-instance.com",
"FLOWISE_API_KEY": "your-api-key"
}
}
}
}
Restart Claude Desktop after adding the configuration.
Available Tools
Flow Management
| Tool | Description |
|---|---|
flowise_list_flows |
List all chatflows and agentflows |
flowise_get_flow |
Get detailed flow configuration |
flowise_create_flow |
Create a new flow |
flowise_update_flow |
Update an existing flow |
flowise_delete_flow |
Delete a flow |
flowise_predict |
Send a message to a flow |
flowise_analyze_flow |
Analyze flow and get improvement suggestions |
Assistants
| Tool | Description |
|---|---|
flowise_list_assistants |
List all configured assistants |
flowise_get_assistant |
Get assistant details and configuration |
Document Stores & Vectors
| Tool | Description |
|---|---|
flowise_list_document_stores |
List all document stores |
flowise_get_document_store |
Get document store details |
flowise_upsert_vector |
Insert/update vectors in a flow |
flowise_query_vector_store |
Search documents in a vector store |
Chat & Configuration
| Tool | Description |
|---|---|
flowise_get_chat_history |
Get conversation history |
flowise_delete_chat_history |
Delete conversation history |
flowise_list_variables |
List global variables |
flowise_list_tools |
List available tools |
flowise_ping |
Check server connectivity |
Usage Examples
"List all my agentflows"
"Send 'Hello' to flow abc123"
"Analyze flow xyz789 and suggest improvements for better accuracy"
"Create a new chatflow named 'Customer Support Bot'"
"Show me all document stores"
"Query the vector store for 'pricing information'"
"Delete chat history for flow abc123"
"List all assistants"
Development
If you want to contribute or run locally:
git clone https://github.com/JuliDir/flowise-mcp.git
cd flowise-mcp
# Using uv
uv sync --extra dev
uv run pytest
# Or using pip
pip install -e ".[dev]"
pytest
Troubleshooting
| Issue | Solution |
|---|---|
| Server not appearing | Restart your AI client |
uvx not found |
Install uv (see step 1) |
| Connection error | Check FLOWISE_BASE_URL |
| Authentication failed | Verify FLOWISE_API_KEY |
License
MIT License - see LICENSE for details.
Author
Julian Di Rocco (@JuliDir)
Metadata
Release files for flowise-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| flowise_mcp-0.1.0.tar.gz | 140.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flowise_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 158.9 kB
Release files / flowise_mcp-0.1.0.tar.gz
| Download URL | flowise_mcp-0.1.0.tar.gz |
|---|---|
| Size | 140.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04c487aa1d3d4da64482f9408af1bb004bca27d751df9a1625e58f8eed73d18a
|
|
BLAKE2b-256 checksum How to use checksums |
8222083b9fff48987a607d4d41c852787ae43c3ab3046cbea2b62ed11f0eaa36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / flowise_mcp-0.1.0-py3-none-any.whl
| Download URL | flowise_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ea2faf651121af055e1004b77ad592b919008608b13d0b3268c8fc2cf45fac7
|
|
BLAKE2b-256 checksum How to use checksums |
66b3947a80a8a37bc6ba3cae64c69b3afc79010fd660e500111caf619ebafbcb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for flowise-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.