n8n MCP Server
Related Servers
Alternatives to n8n MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access comprehensive n8n node documentation, properties, operations, workflow templates, and community nodes, allowing them to design, build, and validate n8n workflows through natural language.46,471 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to access comprehensive n8n node documentation, properties, operations, templates, and validation tools for designing, building, and checking n8n workflows through natural language.746,471 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides AI assistants with comprehensive access to n8n's 525+ workflow automation nodes, including documentation, properties, operations, and 2,500+ templates. Enables creating, validating, and managing n8n workflows through natural language.46,471 npm-
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with comprehensive access to n8n node documentation, properties, and workflow templates. It enables models to search, understand, and manage n8n automation workflows through structured access to over 1,000 node types.46,471 npmMIT
- AlicenseAqualityBmaintenanceProvides AI assistants with comprehensive access to n8n node documentation, properties, operations, templates, and workflow validation for building and managing n8n workflows.746,471 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with comprehensive access to n8n node documentation, properties, operations, and templates, enabling them to build and validate n8n workflows.46,471 npmMIT
TDQS
Scored across 26 tools
Most tools have distinct purposes, but validate_workflow and n8n_validate_workflow are very similar, and n8n_autofix_workflow overlaps with validation. This creates some ambiguity for an agent choosing which tool to use.
The majority of tools use a consistent 'n8n_verb_noun' pattern, but 7 tools lack the prefix (e.g., get_node, validate_workflow), and one tool (validate_node) has no corresponding prefixed version. This mixed convention is still readable but inconsistent.
With 26 tools, the count is on the higher side but justified by the broad domain coverage (workflows, credentials, templates, executions, validation, data tables). Each tool serves a clear purpose, and no tool feels extraneous.
The tool set covers CRUD for workflows, execution management, validation, fixing, versioning, credential and data table management, template deployment, and node configuration. Minor gaps exist (e.g., no explicit export/import), but the surface is largely complete for typical n8n management tasks.