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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- 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/EnmaSuamkf/mcp-flowise'
If you have feedback or need assistance with the MCP directory API, please join our Discord server