mcp-flowise
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOWISE_API_KEY | No | Optional API key if Flowise auth is enabled. | |
| FLOWISE_DYNAMIC | No | Set to 'true' to enable dynamic mode (one tool per chatflow). | false |
| FLOWISE_API_ENDPOINT | Yes | The Flowise API endpoint URL (default: http://localhost:3000). | http://localhost:3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chatflowsA | List the Flowise chatflows available on the configured instance. Returns a JSON array of |
| create_predictionA | Run a Flowise chatflow and return its response. Args:
chatflow_id: Id of the chatflow to run (see |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists available chatflows, the other runs a specific chatflow. There is no overlap or ambiguity.
Both tools follow the verb_noun pattern with consistent snake_case naming (list_chatflows, create_prediction), making them predictable and easy to understand.
With only two tools, the server feels thin for a typical chatflow interaction; while the set covers listing and running, it is on the low end of reasonable scope.
The server lacks essential CRUD operations like creating, deleting, or updating chatflows, which are significant gaps for managing chatflows effectively.