mcp-flowise
Related Servers
Alternatives to mcp-flowise
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceExposes local Flowise chatflows as MCP tools, enabling listing and running chatflows from any MCP client.214 npmMIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables LLM tools to create, manage, and run Flowise chatflows and agentflows programmatically.12MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for interacting with the Langflow API via a natural language interface. It exposes Langflow functionalities as tools for LLMs.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI assistants with access to documentation, schemas, and operations for over 535 n8n workflow automation nodes. It enables models to understand, create, and manage n8n workflows through natural language by connecting to the n8n API.46,471 npmMIT
- AlicenseCqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to Langflow workflow automation platform.100440 npm10MIT

MCP Server Weaviateofficial
FlicenseNot gradedqualityDmaintenanceThe MCP Server for Weaviate facilitates integration with Weaviate using a customizable Python-based server, enabling interaction with Weaviate databases and OpenAI APIs via configurable URL and API keys.163-
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one lists available chatflows, and the other creates predictions using a specific chatflow. There is no overlap in functionality or ambiguity between them.
Both tools follow a consistent verb_noun pattern (list_chatflows, create_prediction) with clear, descriptive names that align with their functions. No deviations or mixed conventions are present.
With only 2 tools, the server feels thin for its apparent domain of interacting with Flowise chatflows. While the tools cover basic operations, the lack of tools for updating, deleting, or managing chatflows suggests an incomplete surface that may limit agent workflows.
The toolset is severely incomplete for a chatflow management domain. It provides listing and prediction creation but lacks essential CRUD operations like creating, updating, or deleting chatflows, as well as tools for managing predictions (e.g., retrieving or canceling them), which will likely cause agent failures in complex tasks.