Migrate to n8n MCP Server
Convert Make and Zapier automations into n8n workflows, with a report of what to check.
Migrate to n8n scores 61 (Good), licensed MIT License. It installs as a local process. It does not declare tools yet. Filed under Uncategorized. Install configs are generated for 10 clients. Being listed in the registry is not the same as being vendor-official.
Good trust
61 of 100 from six public signals. Nobody can buy a point.
- Listed in the official MCP registry.
- License present: mit-license.
License, quality and maintenance
Where the 61 comes from
22 + 20 + 0 + 6 + 10 + 3 = 61. Each factor is capped, so no single signal can carry a listing.
Active in the official MCP registry, plus a known vendor namespace.
Registry: 22 of 30 points.How recently the repository saw a commit or release.
Maintenance: 20 of 20 points.GitHub stars and weekly downloads, on a log scale.
Popularity: 0 of 20 points.A clear, OSI-style open-source license.
License: 6 of 10 points.Not archived, a secure install path, a pinned version.
Security: 10 of 10 points.A real summary, a README with depth, listed tools.
Docs: 3 of 10 points.Install
Pick your client, copy the config, paste it in.
Needs Cursor or VS Code installed on this device. The button opens the app and asks you to confirm before it adds the server.
{ "mcpServers": { "kotiniiqq-migrate-to-n8n": { "command": "npx", "args": [ "-y", "migrate-to-n8n@0.2.0" ], "env": { "MIGRATE_OUTPUT_DIR": "", "N8N_URL": "", "N8N_API_KEY": "YOUR_N8N_API_KEY" } } }}
Environment variables
| Name | Required | Notes |
|---|---|---|
MIGRATE_OUTPUT_DIR | Optional | Folder for converted workflows and reports (default: Documents/migrate-to-n8n) |
N8N_URL | Optional | Your n8n address, to upload results (optional) |
N8N_API_KEYSecret | Optional | n8n API key, to upload results (optional) |
Tools
All capabilitiesTools show up when the registry metadata or the repository README lists them. Public READMEs are read directly. A GitHub token is used only when one is already configured.
About
Convert Make and Zapier automations into n8n workflows, with a report of what to check.
Frequently asked questions
What is Migrate to n8n MCP Server?
Convert Make and Zapier automations into n8n workflows, with a report of what to check.
How do I install Migrate to n8n MCP Server in Claude Desktop, Cursor, or VS Code?
Pick your client in the Install section on this page and copy the generated config into the client's config file. Step-by-step guides: Claude Desktop, Cursor, and VS Code. Migrate to n8n MCP Server runs locally from the npm package migrate-to-n8n with the command npx -y migrate-to-n8n@0.2.0.
Is Migrate to n8n MCP Server free and open source?
Migrate to n8n MCP Server is released under the MIT License license, which is not on MCPpedia's list of OSI-approved open-source licenses. Read the license terms before using it, especially commercially.
Does Migrate to n8n MCP Server support remote (HTTP) connections?
No remote endpoint is listed for Migrate to n8n MCP Server. It runs locally on your machine over stdio, started by your MCP client.
How is Migrate to n8n MCP Server's trust score calculated?
Migrate to n8n MCP Server scores 61 out of 100 (Good). The score adds six capped public signals: registry status, maintenance, popularity, license, documentation, and security. Nobody can pay for points. Read the methodology for the full formula.
Reviews
No reviews yet—Be the first to review
No published reviews yet. Used it? Tell the next person how it went.
Sign inA verified email is required to review this server.
Add badge to your README
Paste either snippet into the repository README. The image links to this listing.
