Nn8n-MCP

Tested npm n8n-mcp 2.102.0 (MIT; community project by czlonkowski, not made by n8n; 23,240 GitHub stars when checked). Runs over stdio in documentation mode with no n8n API key: initialize and tools/list listed 7 tools, all annotated readOnlyHint. Real calls: search_nodes, get_node, validate_node and search_templates all returned results. Workflow-management tools only appear when an n8n instance URL and API key are set; those were not tested. The server prints a telemetry notice on start: anonymous usage telemetry is on by default (opt-out documented in the package PRIVACY.md).
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 4 of 4 documentation-mode calls passed. Workflow-management tools (need an n8n API key) not tested. Evidence: local test run, Nov 11, 2026.

Transport (tested 2026-11-11): stdio

Score 95/100 · Tools 7 · Token cost approx. 1,966 tokens · Compare · Last tested 2026-11-11 · Version tested 2.102.0 · Package n8n-mcp · Repo czlonkowski/n8n-mcp

Summary: n8n-MCP completed an MCP handshake without credentials and exposed 7 tools.

Evidence summary

Handshake

pass

Tools listed

7

Context cost

approx. 1966 tokens, cl100k estimate (7 tools, measured 2026-11-11, version 2.102.0; an estimate) ranking · add up your servers' context cost

API key

No key needed for the tools we called

Tested

2026-11-11

Test results

Local-model readiness

Token cost (estimate): approx. 1966 tokens, cl100k estimate for 7 tools · about 24% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

What we tested and what we didn't

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

{
  "name": "n8n-mcp",
  "version": "2.102.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 7,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install n8n-mcp` (Node 20, Linux) succeeded in 3s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 7 tools listed in 18.7s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 1 days before test; 23,240 GitHub stars."
    ],
    "docs": [
      "partial",
      10,
      "README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y n8n-mcpCopy

Pin the version we tested

npx -y n8n-mcp@2.102.0Copy

tested 2026-11-11. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp@2.102.0"
      ]
    }
  }
}

Tools listed

get_node, get_template, search_nodes, search_templates, tools_documentation, validate_node, validate_workflow

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "n8n-mcp"
      ]
    }
  }
}

Related: Troubleshooting: Protocol version mismatch (HTTP 400)

FAQ

Is n8n-MCP deprecated?

No. n8n-mcp was not deprecated or archived when we last tested it on 2026-11-11.

What replaces n8n-MCP?

Nothing; n8n-MCP is not deprecated as of 2026-11-11.

Does n8n-MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 7 tools.

Embed the badge

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Copy HTML

Copy Markdown Claim this listing · Report an issue