A
licenseC
qualityA
maintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to Langflow workflow automation platform.
100
440 npm
10
MIT
Flowise MCP Server
by wksbx
Related Servers
Alternatives to Flowise MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables AI agents to interact with n8n workflows and automation tools through a standardized interface, allowing execution of workflows and access to n8n functions.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows AI agents to interact with n8n workflows through natural language, enabling workflow management and execution via SSE connections.54 npm7MIT
- AlicenseAqualityDmaintenanceA Python package that implements a Model Context Protocol server for integrating with Flowise API, allowing users to list chatflows, create predictions, and dynamically register tools for Flowise chatflows or assistants.2MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server for programmatically creating and managing n8n workflows.118MIT
TDQS
A3.7/5.0
Scored across 12 tools
Disambiguation4/5
The four create_prediction variants are closely related but have distinct, clearly described purposes (base, with history, with files, with lead). Chatflow management and node exploration tools are clearly separated. The main ambiguity is choosing among the prediction variants, but context usually resolves it.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern. List/get for retrieval, create/update/delete for chatflow operations, and create_prediction for execution. Modifiers like with_history, with_files, and with_lead are appended consistently.
Tool Count5/5
With 12 tools, the server is well-scoped. It covers chatflow CRUD, multiple prediction modes, and node catalog exploration without unnecessary bloat. Each tool serves a clear purpose in the Flowise domain.
Completeness4/5
The tool set provides full lifecycle coverage for chatflows (create, read, update, delete) and a good range of prediction options. It also exposes node catalog information. Minor gaps like lead management or prediction history are not core to the Flowise workflow and can be worked around.
Maintenance
ActivityInactive
ResponsivenessNo issues