Release / / with v2.93.0, v2.94.0, v2.94.1, v2.94.2
n8n-MCP v2.94.3
Target a named n8n instance on each management call when the embedding host provides routing.
Share
Before you upgrade to v2.94.3
2 to fixUse folder names at most 128 characters and omit `[ ] ^ \ / : * ? " < > |`; n8n rejects names outside these rules with 400.
Read the evidence
Workflow telemetry excludes node notes and workflow descriptions; the follow-up also strips sticky-note text, operation descriptions and node-group descriptions from recorded operations and snapshots as applicable.
What changed in v2.94.3
Opt-in `InstanceContext.instanceArgument` advertises an `instance` argument; routing remains the embedder's responsibility. Catalog updates, n8n 2.43 request constraints, IPv6 metadata blocking and telemetry redaction are also covered.
Also: Discover new nodes, connect Agent Slack integrations through managed setup, and keep more free text out of telemetry.
Available through npm or Docker at v2.94.3; npm requires Node.js 20+. Per-call targeting requires an embedding host that enables the argument and implements routing.
New things you can do
Set `InstanceContext.instanceArgument` to true to advertise optional `instance` on management tools; documentation and additional tools are unchanged.
Read the evidence
Fixed and improved
Find Microsoft SharePoint Trigger and Databricks Vector Store; inspect Brevo 1.1's `recipients` rename and Azure AI Foundry Chat Model 1.1's model locator and Responses API switch.
Read the evidence
The refreshed catalog contains 2,295 community nodes, including 184 additions; two rows no longer declared by their packages are omitted.
Read the evidence
On n8n 2.43, Slack connect can omit `credentialId` to start managed setup; follow up with `managerCredentialId` and `workspaceId` through `n8n_manage_agents`.
Read the evidence
URL validation blocks IPv6 cloud metadata endpoints, including alternate address representations, closing the documented metadata-blocking gap.
Seeded by 