Migrate to n8n
NPM · MIGRATE-TO-N8N
Convert Make and Zapier automations into n8n workflows, with a report of what to check.
Available components
Last scanned (7 hours ago)
Scores higher than 48% of npm servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1301 tokens (~216/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/migrate-to-n8n@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_n8n_workflow Check an n8n workflow file ~162
Check an n8n workflow JSON file for problems that stop it from importing or running: broken connections, duplicate node names, disabled steps left, REPLACE-ME placeholders and credentials still to pick. Use it after the user finished steps by hand, or on any n8n workflow. Returns one line per problem (error, warning or info), or "No problems found". Reads the file only; writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | – | The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both. |
| path | string | – | Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both. |
No output schema declared.
No examples provided.
convert_make Convert a Make scenario to n8n ~288
Convert one Make (Integromat) scenario blueprint (the .json from Export Blueprint) into an n8n workflow. Runs locally; nothing is sent anywhere. Writes <scenario name>.n8n.json (import it in n8n), plus the report as Markdown and JSON, to outputDir. Returns the report: totals (converted / to review / manual), every step with its n8n node and status, a concrete suggestion for each step to finish by hand, the credentials and webhook URLs to set up, and the paths of the files. For Zapier exports use convert_zapier instead. Afterwards, upload_to_n8n (when configured) creates the workflow in n8n, and check_n8n_workflow re-checks a file after manual edits.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | – | The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both. |
| outputDir | string | – | Folder to write the results to; created if missing; existing files are kept and the new ones get " (2)", " (3)"… in their name. Default: Documents/migrate-to-n8n in the home folder. |
| path | string | – | Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both. |
No output schema declared.
No examples provided.
convert_zapier Convert Zapier zaps to n8n ~301
Convert zaps from a Zapier export (Settings → Security and data → Download my Zap workflows; one JSON file holds all zaps) into n8n workflows. Runs locally; nothing is sent anywhere. Writes one <zap title>.n8n.json plus a Markdown and JSON report per zap to outputDir, and returns the reports: totals, every step with its n8n node and status, suggestions for the steps to finish by hand, and the file paths. When the export holds many zaps, call list_zaps first and pass the chosen titles or ids in "zaps". For Make blueprints use convert_make instead.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | – | The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both. |
| outputDir | string | – | Folder to write the results to; created if missing; existing files are kept and the new ones get " (2)", " (3)"… in their name. Default: Documents/migrate-to-n8n in the home folder. |
| path | string | – | Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both. |
| zaps | array | – | Titles or ids of the zaps to convert, as list_zaps shows them; titles match without regard to case. Leave out to convert every zap in the export. |
No output schema declared.
No examples provided.
list_zaps List the zaps in a Zapier export ~141
List the zaps in a Zapier export without converting anything: id, title, number of steps, apps used and on/off state of each. Use it before convert_zapier when the export holds more than a few zaps, so the user can choose which ones to convert. Reads the file only; writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | – | The full contents of the exported file, when the user pasted or attached it instead of giving a path. Give either path or json, not both. |
| path | string | – | Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both. |
No output schema declared.
No examples provided.
suggest_replacement How to replace a Make module or Zapier step ~158
Explain how one Make module or Zapier step is handled, without converting a file: whether it converts automatically and to which n8n node, or which n8n app node, HTTP request to the app's API, or Code node to use instead, with the steps to set it up. Use it when the user asks about a single module, or to explain a step a report marked review or manual.
| Name | Type | Req | Description |
|---|---|---|---|
| module | string | yes | The module or step key exactly as the export or the report shows it, e.g. "slack:CreateMessage" for Make or "SlackCLIAPI:channel_message" for Zapier. |
| source | string | yes | Where the module comes from: "make" or "zapier". |
No output schema declared.
No examples provided.
supported_modules What converts automatically ~146
List the Make modules and Zapier steps that convert automatically, as a table of module key and the n8n node it becomes. Use it to answer "does X convert?" before the user exports anything; for one known key, suggest_replacement gives more detail. Modules not listed still convert to a placed, disabled n8n node with a suggestion.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Text to look for in the module key or the n8n node name, without regard to case, e.g. "sheets" or "slack". Leave out to list everything. |
| source | string | – | Only "make" or only "zapier". Leave out for both. |
No output schema declared.
No examples provided.
How do I install the Migrate to n8n MCP server?
Migrate to n8n runs locally as an npm package, launched with npx -y migrate-to-n8n. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · migrate-to-n8n
claude mcp add kotiniiqq-migrate-to-n8n -- npx -y migrate-to-n8n
What is the Migrate to n8n MCP server?
Migrate to n8n is an MCP server listed in the public MCP registry as io.github.kotiniiqq/migrate-to-n8n. Convert Make and Zapier automations into n8n workflows, with a report of what to check. This page covers its npm package (migrate-to-n8n).
Is the Migrate to n8n MCP server safe to use?
Migrate to n8n scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Migrate to n8n MCP server expose?
Migrate to n8n exposes 6 tools: convert_make, convert_zapier, list_zaps, suggest_replacement, supported_modules, check_n8n_workflow. Their descriptions and schemas cost roughly 1,196 tokens of context every time the server is loaded.
Is the Migrate to n8n MCP server still maintained?
Migrate to n8n is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Migrate to n8n MCP server under?
Migrate to n8n declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.