n8n-mcp-mini
Related Servers
Alternatives to n8n-mcp-mini
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access comprehensive n8n node documentation, schemas, operations, and validation tools, and optionally create, update, and execute workflows through the n8n API.49,825 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to access comprehensive n8n node documentation, properties, operations, templates, and validation tools for designing, building, and checking n8n workflows through natural language.749,825 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search, validate, and manage n8n workflows, providing structured access to over 1,800 node documentations and templates.2649,825 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with structured access to n8n node documentation, properties, operations, and validation tools so they can build and troubleshoot workflows; with API credentials, it can also create, update, and execute workflows.49,825 npmMIT
- 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.49,825 npmMIT
- AlicenseAqualityCmaintenanceProvides AI assistants with comprehensive access to n8n node documentation, properties, operations, templates, and workflow validation for building and managing n8n workflows.749,825 npmMIT
TDQS
Scored across 27 tools
The management tools (n8n_*) are distinct, but there is notable overlap among the validation tools: validate_workflow, validate_workflow_connections, validate_workflow_expressions, and n8n_validate_workflow all serve similar purposes with subtle differences. The distinction between n8n_validate_workflow (fetches by ID) and validate_workflow (takes a definition) could confuse an agent.
The n8n_ prefix is applied to management tools but not to exploration/validation tools (e.g., search_nodes, validate_workflow), creating a mix. Also, n8n_validate_workflow and validate_workflow break the pattern by having the same base name with one prefixed, making the naming scheme unpredictable.
At 27 tools, this exceeds the 'too many' threshold of 25. The count is partially justified by covering both live instance management and a large node schema database, but many validation variants (4+ tools) bloat the surface and could be consolidated.
The server covers the full lifecycle for workflows (create, read, update, delete, activate) and credentials (except update), plus executions and extensive node validation. Minor gaps like missing credential update and execution retry are workarounds, but overall the domain is well-covered.