osfeed.dev
Use with your agentConnect an agent
Projects/n8n-MCP/v2.54.0
Release / / with v2.52.0, v2.53.0, v2.53.1, v2.53.2

n8n-MCP v2.54.0

Inspect the published workflow graph separately from its draft.

Share
XRedditHacker NewsBlueskyLinkedIn
All of n8n-MCP

Before you upgrade to v2.54.0

1 to fix

Treat `get_node`'s standard-detail version field as a number, not a string; remove string-only operations before using it as `typeVersion`.

Action requiredFind n8n nodes, their settings, operations, documentation and example configurations.Affects: Clients parsing get_node version fields
Read the evidence

Partial-update operations run in their supplied order so connection edits before node renames remain valid.

Behavior changedCreate, inspect, edit and delete workflows on an n8n instance.Affects: Callers batching node and connection edits
Read the evidence

What changed in v2.54.0

Inspect the published workflow graph separately from its draft.

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

New things you can do

Fixed and improved

`n8n_get_workflow`(mode='active') returns the published graph; ordinary reads omit the duplicate `activeVersion` graph.

ImprovedCreate, inspect, edit and delete workflows on an n8n instance.
Read the evidence

Community-node lookup stops presenting npm package versions as workflow `typeVersion` values.

Now worksSearch community nodes and read their available documentation.
Read the evidence

Public IPv4 services can be reached through supported `DNS64`/`NAT64` synthesized IPv6 addresses.

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

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

Share

LinkedIn takes the link and its card only; write your text there.

X LinkedIn Reddit Hacker News Bluesky