Flowise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOWISE_API_KEY | Yes | API key from Flowise (Settings > API Keys) | |
| FLOWISE_BASE_URL | No | URL where your Flowise instance is running | http://localhost:3000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_predictionB | Run a Flowise chatflow with a question and get a response. Use this to interact with AI workflows configured in Flowise. |
| create_prediction_with_historyB | Run a Flowise chatflow with conversation history for context-aware responses. |
| create_prediction_with_filesB | Run a Flowise chatflow with file attachments (images, documents, etc.). |
| create_prediction_with_leadB | Run a Flowise chatflow and capture a lead email for the conversation. |
| list_chatflowsA | List all chatflows available in Flowise. Returns chatflow IDs, names, and metadata. |
| get_chatflowA | Get a specific chatflow by ID, including its full configuration with nodes and edges. |
| create_chatflowC | Create a new chatflow in Flowise with specified nodes and edges configuration. |
| update_chatflowA | Update an existing chatflow's configuration, nodes, edges, or metadata. |
| delete_chatflowA | Delete a chatflow from Flowise. This action is irreversible. |
| list_nodesA | List all available node types in Flowise that can be used to build chatflows. |
| get_nodes_by_categoryA | Get all nodes in a specific category (e.g., 'Chat Models', 'Agents', 'Memory', 'Tools'). |
| get_nodeB | Get detailed information about a specific node type by its name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/wksbx/flowise-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server