Name: Migrate to n8n
Author: kotiniiqq

Migrate to n8n MCP

Convert Make and Zapier automations into n8n workflows, with a report of what to check.

Grade A Local · stdio No auth needed 7 tools v0.2.0 MIT

No reviews yet by kotiniiqqnpm 489 Runs on your machine, nothing hosted

96/100

trust score

downloads a day

local

runs on your machine

489

downloads in 30d

What it does

Convert Make and Zapier automations into n8n workflows, with a report of what to check.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user migrate-to-n8n-mcp '--' npx -y migrate-to-n8n serve

# 2 — ask your agent for something these tools do
#   convert_make, convert_zapier, list_zaps and 4 more

Migrate to n8n costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

kotiniiqq2 servers

2 categories

All 2 servers

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Migrate to n8n as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user migrate-to-n8n-mcp '--' npx -y migrate-to-n8n serve

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take MIGRATE_OUTPUT_DIR (Folder for converted workflows and reports (default: Documents/migrate-to-n8n)), N8N_URL (Your n8n address, to upload results (optional)), N8N_API_KEY (n8n API key, to upload results (optional)) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Parameter	Type	Required	Notes
outputDir	string	no	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.

Parameter	Type	Required	Notes
zaps	array	no	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.
outputDir	string	no	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.

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.

Parameter	Type	Required	Notes
path	string	no	Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both.
json	string	no	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.

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…

Parameter	Type	Required	Notes
source	string	yes	Where the module comes from: "make" or "zapier".
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.

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,…

Parameter	Type	Required	Notes
source	string	no	Only "make" or only "zapier". Leave out for both.
query	string	no	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.

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…

Parameter	Type	Required	Notes
path	string	no	Absolute path of the exported file on this computer (~ is the home folder). Give either path or json, not both.
json	string	no	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.

Create a converted workflow (a .n8n.json file) as a new workflow in the user's n8n at …, through the n8n API. It is created inactive with " (migrated)" in its name; existing workflows are never changed, and calling it twice creates two copies. Returns the link to open it. Use it after convert_make…

Parameter	Type	Required	Notes
path	string	yes	Path of the .n8n.json file that convert_make or convert_zapier wrote (shown under "Files" in their result).

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Migrate to n8n or to call it, at any volume.

ATrust score 96 / 100

Release 0.2.0 · scanned 28 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings0 threat · 0 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digest53ffb5b0b8c7f618a70e4e13e614ffba4333314c9d2016c9f65ae1ab0b7a9a50

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

1 of the 7 recovered tools are registered only when upload holds (dist/mcp/server.js:136) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

6 tools are registered unconditionally · 1 more only when upload holds (dist/mcp/server.js:136) — typically when a key or option is configured. All 7 are in the table below and were analysed; the conditional ones are marked.

Tool	Capability tags	Why the tag was assigned
convert_make	state-write	state-write: declares readOnlyHint: false
convert_zapier	state-write	state-write: declares readOnlyHint: false
list_zaps	no tags
suggest_replacement	external-sink	external-sink: keyword "http_request"
supported_modules	no tags
check_n8n_workflow	no tags
upload_to_n8n conditional	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest53ffb5b0b8c7f618

Scanned2026-10-28

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.