mcp-flowise

MIT License

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`FLOWISE_API_KEY`	Yes	Your Flowise API Bearer token.
`FLOWISE_CHATFLOW_ID`	No	Single Chatflow ID (optional).
`FLOWISE_API_ENDPOINT`	Yes	Base URL for Flowise. Default is 'http://localhost:3000'.	http://localhost:3000
`FLOWISE_ASSISTANT_ID`	No	Single Assistant ID (optional).
`FLOWISE_CHATFLOW_BLACKLIST`	No	Comma-separated list of denied chatflow IDs (optional).
`FLOWISE_CHATFLOW_WHITELIST`	No	Comma-separated list of allowed chatflow IDs (optional).
`FLOWISE_CHATFLOW_DESCRIPTIONS`	No	Comma-separated list of 'chatflow_id:Description' pairs for LowLevel mode.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

Functions exposed to the LLM to take actions

Name	Description
list_chatflows	List all available chatflows from the Flowise API. This function respects optional whitelisting or blacklisting if configured via FLOWISE_CHATFLOW_WHITELIST or FLOWISE_CHATFLOW_BLACKLIST. Returns: str: A JSON-encoded string of filtered chatflows.
create_prediction	Create a prediction by sending a question to a specific chatflow or assistant. Args: chatflow_id (str, optional): The ID of the chatflow to use. Defaults to FLOWISE_CHATFLOW_ID. question (str): The question or prompt to send to the chatflow. Returns: str: The raw JSON response from Flowise API or an error message if something goes wrong.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matthewhand/mcp-flowise'

If you have feedback or need assistance with the MCP directory API, please join our Discord server