n8n-mcp — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of npm/n8n-mcp: Have workflow create/update/delete and execution tools changed their authentication or read-only separation?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Understand and configure n8n automation workflows

What we know

Community n8n node/documentation and workflow development MCP.

Maintenance / activity evidence

n8n-mcp v2.89.0 was released 2026-09-23.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Documentation tools need no n8n API key. Management tools require N8N_API_URL and N8N_API_KEY; can create/update/delete workflows and execute automations. Instance-level N8N_MCP_ACCESS_TOKEN is separate and optional for specific functions. Writes: Create or update n8n workflows when management tools and API credentials are enabled; Delete n8n workflows when the relevant management tool is authorized; Trigger/execute workflows when exposed by the enabled tools.
Authentication not yet verified.
With n8n API credentials, can create/modify/delete workflows, trigger execution, and affect downstream connected accounts.

With n8n API credentials, can create/modify/delete workflows, trigger execution, and affect downstream connected accounts.
Advisory/security review not completed; no safety badge.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

23,052 shared-repository stars · 420.2k package downloads / 30 days

Stars observed Oct 9, 2026. Downloads observed Oct 9, 2026.

Repository total for czlonkowski/n8n-mcp; not package-specific.

Exact npm package n8n-mcp; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Have workflow create/update/delete and execution tools changed their authentication or read-only separation?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

With n8n API credentials, can create/modify/delete workflows, trigger execution, and affect downstream connected accounts.
Advisory/security review not completed; no safety badge.
Documentation tools need no n8n API key. Management tools require N8N_API_URL and N8N_API_KEY; can create/update/delete workflows and execute automations. Instance-level N8N_MCP_ACCESS_TOKEN is separate and optional for specific functions.
Reviewed write actions: Create or update n8n workflows when management tools and API credentials are enabled; Delete n8n workflows when the relevant management tool is authorized; Trigger/execute workflows when exposed by the enabled tools
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
n8n API access can modify and execute real workflows; documentation-only and management paths have different authority.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
first-party data processing and retention
data retention and permission scope
AI-edited production workflows can cause damaging writes; some features need N8N_API_KEY.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

n8n-mcp v2.89.0 was released 2026-09-23.

Technical identity

npm/n8n-mcp

Exact implementation source: https://www.npmjs.com/package/n8n-mcp ↗
Reviewed resource type: MCP Server
Repository identity: czlonkowski/n8n-mcp
Package identity: npm:n8n-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
czlonkowski/n8n-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.
Package registry ↗
n8n-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
n8n-mcp can expose credential and workflow mutation tools; read-only mode and scopes should be selected intentionally. A documents a route, not that n8n auth was tested.
Install documentation is not a guarantee of current package/runtime compatibility.
Publisher n8n-mcp is an independently deployable MCP bridge with documented local/remote setup. n8n REST API token and optional n8n instance-level MCP token are DIFFERENT.
Do not mix them or assume every tool needs both.
Never create/delete workflows as an installation check. (Documentation review only, not runtime verified.)
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y n8n-mcp
Configure / authenticate
MCP100 setup guide
Follow publisher self-hosted or hosted installation guide; run local stdio/Docker as chosen. Optional N8N_API_URL and N8N_API_KEY for workflow management; N8N_MCP_ACCESS_TOKEN is separate.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: For n8n REST workflow tools set N8N_API_URL and N8N_API_KEY; for supported native instance-level MCP functionality additionally enable MCP in n8n Settings and set N8N_MCP_ACCESS_TOKEN. Do not mix them or assume every tool needs both.
Check connection
Suggested check
Confirm n8n-MCP tools are listed; read node/tool info before invoking workflow mutations.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `n8n-mcp` in Claude Code, remove its exact client entry with `claude mcp remove n8n-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove n8n-mcp

Official Documentation & Sources

What it does

Community n8n node/documentation and workflow development MCP.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Understand and configure n8n automation workflows

Representative uses

Node schemas
examples
optional n8n instance operations

Limitations

AI-edited production workflows can cause damaging writes; some features need N8N_API_KEY.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Documentation tools need no n8n API key. Management tools require N8N_API_URL and N8N_API_KEY; can create/update/delete workflows and execute automations. Instance-level N8N_MCP_ACCESS_TOKEN is separate and optional for specific functions.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: With n8n API credentials, can create/modify/delete workflows, trigger execution, and affect downstream connected accounts.

Access scope and cautions

Write actions: Create or update n8n workflows when management tools and API credentials are enabled Delete n8n workflows when the relevant management tool is authorized Trigger/execute workflows when exposed by the enabled tools
Risk level: high
Security notes: Advisory/security review not completed; no safety badge.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Node schemas; examples; optional n8n instance operations.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio, streamable_http. Client notes: Codex /mcp: check server status and tools; inspect read-only docs tools without credentials first. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Knowledge tools can operate without an n8n API key; workflow management requires n8n URL/API key. HTTP deployment requires AUTH_TOKEN.

Can it modify data or perform write operations?

Documented write actions include: Create or update n8n workflows when management tools and API credentials are enabled; Delete n8n workflows when the relevant management tool is authorized; Trigger/execute workflows when exposed by the enabled tools. Recorded permission boundary: Documentation tools need no n8n API key. Management tools require N8N_API_URL and N8N_API_KEY; can create/update/delete workflows and execute automations. Instance-level N8N_MCP_ACCESS_TOKEN is separate and optional for specific functions.

What limitations and risks should I check before use?

With n8n API credentials, can create/modify/delete workflows, trigger execution, and affect downstream connected accounts. AI-edited production workflows can cause damaging writes; some features need N8N_API_KEY. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. n8n API access can modify and execute real workflows; documentation-only and management paths have different authority. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.