migrate-to-n8n
Related Servers
Alternatives to migrate-to-n8n
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceProvides seamless integration between MCP-compatible AI assistants and n8n workflow automation, enabling intelligent management and automation of n8n workflows through natural language.5-
- AlicenseAqualityAmaintenanceProvides ops-focused n8n tools for MCP-compatible agents, enabling listing, inspecting, triggering, validating, managing tags, running security audits, and safely editing n8n workflows with auto-backup and confirm gates.2016 npm1MIT
- FlicenseBqualityBmaintenanceEnables AI assistants to fully automate n8n instances via 34 MCP tools, covering workflow creation, execution debugging, credential management, environment variables, tags, and user administration through natural language.341-
- AlicenseNot gradedqualityDmaintenanceEnables management of multiple N8N workflow automation instances through MCP. Supports listing, creating, updating, deleting, executing workflows and monitoring their executions across different N8N environments.80 npmMIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that provides full control over n8n automation workflows through natural language. It offers 43 tools for managing workflows, executions, credentials, and data tables, with safety features like write-mode protection and double-validated workflow creation.431MIT
- AlicenseAqualityCmaintenanceEnables management of n8n workflows, executions, credentials, tags, and variables via MCP tools. Supports stdio, Claude Code, and Claude Web with optional Authentik OAuth.22MIT
TDQS
Scored across 6 tools
Conversion tools are cleanly split by source (Make vs Zapier) and explicitly cross-reference each other, and list_zaps/check_n8n_workflow have clearly distinct jobs. The only mild overlap is between supported_modules and suggest_replacement, which both answer 'does X convert?', though the descriptions do explain when to use which.
Most tools follow a verb_noun pattern (convert_make, convert_zapier, list_zaps, suggest_replacement, check_n8n_workflow) with consistent snake_case. supported_modules is a noun-only outlier, a minor deviation from the otherwise predictable scheme.
Six tools is well-scoped for a converter: two conversion entry points, one listing helper, two explanation/lookup tools, and one validator. Each earns its place with no filler.
The surface covers convert, inspect, explain, and validate, but convert_make's description points to an upload_to_n8n tool that is not in the set, creating a dead-end reference for pushing workflows into n8n. There is also no tool for editing or fixing an output file beyond re-checking it.