Release / 9 Aug 2026 / with v2.68.2, v2.68.3, v2.68.4

n8n-MCP v2.69.0

Read the supporting assets referenced by bundled workflow guides.

Before you upgrade to v2.69.0

1 to fix

Instances in newly blocked address ranges such as 100.64.0.0/10 need a permitted endpoint or `WEBHOOK_SECURITY_MODE`=permissive; that setting broadly re-allows private ranges.

Action requiredConnect an MCP client to node documentation and optional n8n management tools.Affects: Strict/moderate deployments using shared-address, multicast or reserved ranges

Read the evidence

czlonkowski/n8n-mcp/blob/v2.69.0/CHANGELOG.md

Telemetry flushes every 60 seconds instead of 5, and mutation telemetry no longer sends the pre-mutation workflow.

Behavior changedAffects: Telemetry-enabled deployments

Read the evidence

czlonkowski/n8n-mcp/blob/v2.68.2/CHANGELOG.md

What changed in v2.69.0

Read the supporting assets referenced by bundled workflow guides.

Available through npm or Docker at v2.69.0. Instance management requires configured n8n API access.

Fixed and improved

Bundled skills include referenced self-hosting templates and supporting assets.

Now worksRead bundled n8n workflow guidance through MCP Resources.

Read the evidence

czlonkowski/n8n-mcp/blob/v2.68.4/CHANGELOG.md

The first-run telemetry notice and embedded-server logging no longer corrupt stdio `JSON`-RPC.

Now worksConnect an MCP client to node documentation and optional n8n management tools.

Read the evidence

czlonkowski/n8n-mcp/blob/v2.68.3/CHANGELOG.md

Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.