A
licenseB
qualityC
maintenanceA Model Context Protocol server that enables AI assistants to interact with N8N workflows, executions, and automation capabilities.
12
MIT
langflow-mcp-server
Related Servers
Alternatives to langflow-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables LLM tools to create, manage, and run Flowise chatflows and agentflows programmatically.12MIT
- 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.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations, enabling them to build and validate workflows.141,724 npmMIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with n8n workflows through natural language, supporting actions like listing, creating, updating, executing and monitoring workflows.329 npm1,635MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges AI assistants like Claude with Wordware's specialized agent capabilities, allowing dynamic loading and access to any Wordware flow through a standardized interface.-
TDQS
C2.8/5.0
Scored across 216 tools
Disambiguation1/5
Multiple tools appear to do the same thing: run_flow/run_workflow/run_flow_advanced/process_flow/predict_flow, list_files/list_files_v2, delete_file/delete_file_v2, and upload_knowledge_base/ingest_knowledge_base are near-duplicates from an agent's perspective. With 216 tools, the boundary between monitor messages, shared messages, sessions, and workflow variants is extremely unclear.
Naming Consistency2/5
The majority of tools use readable snake_case verb_noun names, but the pattern is undermined by legacy endpoints like process_flow, predict_flow, and build_vertices, plus versioned variants such as list_files_v2 next to list_files. Different verb styles and deprecated tools make the naming inconsistent enough to cause confusion.
Tool Count1/5
216 tools is an extreme count for a single MCP server and is far beyond any reasonable curated surface. This looks like a full API dump rather than a coherent tool set, creating massive context overhead and expensive tool-selection decisions for agents.
Completeness4/5
The set is remarkably broad and covers CRUD/lifecycle operations for flows, folders, projects, variables, knowledge bases, files, users, roles, memory, MCP config, and traces. Minor gaps exist, such as no update operation for knowledge bases or store components, and some deprecated endpoints add noise, but the domain is largely covered.
Maintenance
ActivityMaintained
ResponsivenessSlow