mcp-n8n
Related Servers
Alternatives to mcp-n8n
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access n8n node documentation, properties, and operations for 535+ workflow automation nodes, and optionally create, update, and execute n8n workflows through the n8n API. Supports building n8n workflows for Claude Desktop, Claude Code, Windsurf, and Cursor.83,221 npmMIT
- AlicenseBqualityDmaintenanceEnables users to manage workflows, monitor executions, and perform administrative tasks in n8n through natural language conversations with Claude. It provides over 40 tools to control self-hosted or cloud n8n instances via the Model Context Protocol.4280 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage n8n automation workflows through natural language commands, including creating, executing, monitoring, and organizing workflows with full CRUD operations and execution management.56 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of n8n workflow automations through natural language, supporting creation, execution, updates, and deletion of workflows, along with node discovery and execution status monitoring.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to build, execute, and manage n8n Cloud workflows conversationally, from writing workflow JSON through running, debugging, and exporting it. Access is confined by a name-prefix guard so it can only ever touch the workflows and credentials it created itself.MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to create, manage, and monitor n8n workflows through natural language using AI interfaces like Claude and Cursor. It supports multi-instance environments and provides tools for workflow lifecycle management, execution monitoring, and tag organization.50 npm236MIT
TDQS
Scored across 61 tools
Most tools map cleanly to a resource and action, but a few boundaries blur: n8n_update_workflow vs n8n_update_workflow_partial, n8n_get_workflow_template vs n8n_search_public_templates, and the various workflow listing variants can lead agents to pick the wrong one. Descriptions help, but the overlap is real.
Nearly all tools follow the n8n_verb_noun pattern with predictable list/get/create/update/delete groups. Minor deviations like n8n_workflow_health (no verb), n8n_debug_last_error, and the plural n8n_create_users keep it from being fully consistent.
61 tools is far above the 25+ threshold and feels heavy for an agent-facing surface. The n8n domain is broad, but several utilities such as the workflow list vs summary, update vs partial update, and snapshot/backup/export tooling could be consolidated.
Workflows, executions, tags, variables, users, and projects have solid CRUD/lifecycle coverage. However, credentials are missing list/get/update operations, and source control only supports pull, leaving notable gaps for a full n8n management server.