n8n Workflow Builder MCP Server
Related Servers
Alternatives to n8n Workflow Builder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).3358 npm119MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that generates production-ready n8n workflows from natural language prompts. Transform simple descriptions into fully validated, deployable automation workflows using AI-powered code generation.1-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) server for managing n8n workflows, allowing Claude and other MCP-compatible tools to create, read, update, delete, and execute workflows in your n8n instance.90 npmMIT
- 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 complete Model Context Protocol server that enables Claude to create, manage, and execute n8n workflows through conversational AI.1MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with N8N workflows, executions, and automation capabilities.12MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'create_workflow' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming pattern is perfectly consistent as there is only one tool. It follows a clear verb_noun convention ('create_workflow'), which would be easy to maintain if more tools were added.
A single tool is insufficient for a 'Workflow Builder' server, which implies capabilities like listing, updating, executing, or deleting workflows. This feels thin and under-scoped for the apparent domain of workflow management.
The tool surface is severely incomplete for workflow building. It only offers creation, with no ability to read, update, delete, execute, or manage existing workflows. This creates significant dead ends for agents trying to perform basic lifecycle operations.