Safety
n8n-mcp: newer Node.js needed, security fixes in 2.99.1
n8n-mcp now asks for a patched Node.js 22, 24 or 26. Versions 2.98.1 to 2.99.1 fix security issues, including credentials that could reach telemetry.
- Date
- Works with
- Claude Code, Codex CLI, Gemini CLI
What’s new
n8n-mcp 2.96.2 came out on 23 October 2026. It now asks for Node.js ^22.23.4, ^24.22.1 or >=26.12.1. Before, any Node.js 20 or newer was fine. The changelog says this follows the October 2026 Node.js security release, and that Node 20 is end-of-life. It also says: "npm only warns on a mismatch unless `engine-strict` is set."
Versions 2.98.1 to 2.99.1 came out on 24 and 25 October 2026. The changelog lists security fixes for "prototype pollution in the workflow auto-fixer" (2.98.1), "credentials and personal data reaching telemetry and server logs" (2.99.0), and denial of service through crafted input, mostly in shared HTTP deployments (2.99.0 and 2.99.1). Telemetry now also redacts more values, such as short keys and personal data in node names. The changelog names GitHub security advisories for these fixes, but on 26 October 2026 they were not public yet.
Why it matters
Telemetry is on by default, so credentials or personal data from your workflows could reach telemetry or the server's logs before 2.99.0. Update n8n-mcp, or switch its telemetry off. On an older Node.js, npm shows a warning, and you run without the Node.js security fixes.
How to try it
Run node --version. If it is older than 22.23.4, 24.22.1 or 26.12.1, update Node.js first. Then name the version when you start the server, for example npx [email protected]. To switch telemetry off, run npx n8n-mcp telemetry disable, or set N8N_MCP_TELEMETRY_DISABLED=true.
Related
Source
Checked against the source on 26 Oct 2026