Repository navigation
Releases
v0.3.1
Version 0.3.1 is a frozen release candidate. Availability is established only
by matching npm provenance, GitHub Release assets and signatures, and MCP
Registry readbacks; this immutable entry is not rewritten after publication.
Security
- The reviewed runtime lock graph now resolves patched
fast-uri,hono,
ip-address, andqsreleases, clearing the complete npm production audit
instead of applying the incomplete package-by-package Dependabot proposals. - CodeQL initialization and analysis now use the same immutable v4.38.2 commit,
avoiding mixed-version workflow failures. - The release toolchain no longer loads the vulnerable, unfixed
node-forge
dependency pulled by the upstream MCPB CLI. It validates the pinned official
v0.4 schema, creates and extracts bounded canonical ZIPs locally, and keeps
CMS signing and verification on OpenSSL.
Changed
- Current compatible development releases of
@types/node, ESLint,globals,
Prettier,typescript-eslint, andyamlkeep the verification toolchain
current without changing the public 44-tool MCP contract.
v0.3.0
Version 0.3.0 is a frozen release candidate. Availability is established only
by matching npm provenance, GitHub Release assets and signatures, and MCP
Registry readbacks; this immutable entry is not rewritten after publication.
Removed
- Breaking input-schema change:
n8n_audit_generateno longer publishes or
acceptsdaysAbandonedWorkflow. n8n Community 2.30.x stores that request
override in a legacy setting while the reporter reads typed instance
configuration, so the input could not reliably change the audit. Normal MCP
clients refresh the smaller schema after reconnecting; raw callers must stop
sending the removed field, omit empty category arrays, and deduplicate category
names. This incompatible0.xchange is released as a new minor version.
Changed
n8n_audit_generatenow publishes truthful read-only and idempotent safety
hints while retaining the conservative unsafe authorization gate for its
sensitive instance-wide report. It makes one request, accepts 1–5 unique
categories, treats n8n's empty-array clean result as an empty report, and
accepts nullable version metadata from n8n's version feed. It fails
explicitly instead of returning a partial audit when sanitizer or final
256 KiB result limits are exceeded; multi-category callers can retry with
fewer categories, while single-category callers can review the full report in
n8n.- Sanitized read results now distinguish content redaction from size reduction.
Audit reports use validated higher collection bounds within the same final
256 KiB envelope, while ordinary read tools keep safe bounded projections. - The generic 256 KiB ceiling now covers the complete serialized MCP result,
including text and structured content. Large reads that previously fit only
the text-side check now fail safely; already-applied mutations return a
bounded success summary withtruncated=trueandredacted=true. - Record parsing now preserves own
__proto__keys through validation and
rewrites prototype-like output keys safely. Workflow updates retain those
graph entries instead of silently dropping them. - Development dependency
globalswas updated from 17.8.0 to 17.9.0.
v0.2.1
What changed
- Improved 40 tool definitions with clearer selector semantics, authorization boundaries, side effects, pagination behavior, and return contracts.
- Strengthened the durable 44-tool definition matrix across parameters, authorization, configuration, returns, annotations, and task support.
- Added controlled mutations that prove every definition invariant fails when its contract drifts.
- Clarified execution-stop states and the opt-in required for remote plaintext HTTP health checks.
Install or update
npm install --global n8n-mcp-community@latestRestart your MCP client after updating so it reloads the tool definitions.
Verification
This release is published through npm Trusted Publishing with provenance, an immutable GitHub Release, a signed MCPB bundle, checksums, an SBOM, and MCP Registry metadata. See the provenance guide for verification steps.
Full details: CHANGELOG.md
v0.2.0
n8n MCP Community v0.2.0
This release makes the MCP easier to install and simpler to authorize while
preserving its security-focused, local stdio design and complete 44-tool n8n
Community Edition surface.
Highlights
- Makes
npm install --global n8n-mcp-community@latestthe primary install
path, with copyable npx and signed MCPB alternatives. - Rebuilds the README as a short path from value to installation, connection,
proof, and deeper documentation. - Makes
N8N_MCP_MODE=unsafethe complete server-side gate for the 14 elevated
tools. Mode separation, tool annotations, API-key permissions, input
validation, and metadata-only audit events remain in place. - Replaces the old demo with a deterministic, synthetic walkthrough of
installation, connection, and an actionable Introspect finding. - Passes 296 automated tests plus Linux, macOS, Windows, CodeQL, Semgrep,
Trivy, Gitleaks, dependency, package, MCPB, documentation, and Registry
gates.
Breaking change for raw callers
The 14 unsafe tools no longer publish or accept the former confirmation
input. Normal MCP clients refresh the schema after reconnecting. Custom code
that sends raw tool-call JSON must remove that field.
Connection URLs, API keys, transport settings, and the read-only, write,
and unsafe mode values do not change.
Upgrade from 0.1.x
- Global npm: rerun
npm install --global n8n-mcp-community@latest. - Pinned npx: replace
n8n-mcp-community@0.1.4with
n8n-mcp-community@latestorn8n-mcp-community@0.2.0. - MCPB: install the new signed bundle from this release.
- Restart the MCP client and confirm the server reports version
0.2.0.
See the installation guide
and frozen changelog entry
for complete details and rollback instructions.
v0.1.4
n8n MCP Community v0.1.4\n\nThis definition-quality and privacy patch release preserves the complete 44-tool n8n Community Edition surface and the local-first, stdio-only design.\n\n### Highlights\n\n- Rewrites all 44 tool definitions in native-quality English with explicit side effects, authorization boundaries, compatibility constraints, return contracts, and tool-specific semantics.\n- Prevents upstream credential-test diagnostic text from reaching MCP output; only fixed server-authored success or error messages are returned.\n- Distinguishes five reviewed additive or non-destructive operations from destructive mutations while preserving the independent read-only, write, and unsafe authorization classes.\n- Adds a complete 44-tool definition matrix over the final tools/list surface, with controlled mutations proving every invariant can fail.\n- Retains the Glama score badge and updates the reviewed synthetic demo to v0.1.4.\n- Passes 295 automated tests plus Linux, macOS, Windows, CodeQL, Semgrep, Trivy, Gitleaks, dependency, package, MCPB, documentation, and Registry gates.\n\n### Security note\n\nThe signed MCPB is verified against the repository-pinned certificate policy and is byte-identical to the reviewed unsigned payload after removing its canonical signature block. Consumers must still use a dedicated least-privilege n8n API key and select the narrowest safety mode that meets their needs.\n\nSee the frozen changelog entry for complete details.
v0.1.3
n8n MCP Community v0.1.3
This security-focused patch release updates the dependency and verification
chain while preserving the complete 44-tool n8n Community Edition surface and
the local-first, stdio-only design.
Highlights
- Upgrades the MCP SDK to 1.30.0 and removes the temporary downstream Hono
override. A clean standalone consumer now resolves patched Hono 2.x and
passes a production audit with no advisories. - Updates the reviewed lockfile to patched
fast-uri,hono,ip-address,
and development-onlybrace-expansionreleases. - Makes root and disposable-consumer audits fail closed against hostile ambient
npm registry, proxy, TLS, CA, and configuration overrides. - Adds a version-to-GIF review history anchored to immutable annotated release
tags, preventing stale or rewritten public demo evidence. - Replaces a newly unavailable Keyv source link with the immutable exact-version
npm registry record. - Passes 292 automated tests plus Linux, macOS, Windows, CodeQL, Semgrep, Trivy,
Gitleaks, dependency, package, MCPB, documentation, and Registry gates.
Security note
The reviewed repository, signed MCPB, and clean standalone npm consumer audit
without known advisories. Projects that embed this package into a larger
dependency graph must still audit their final resolved graph independently.
See the frozen changelog entry
for complete details.
v0.1.2
n8n MCP Community v0.1.2
This release strengthens the complete 44-tool Community Edition surface while preserving the local-first, stdio-only design.
Highlights
- Tool-specific descriptions, safe-use boundaries, sibling alternatives, return semantics, and top-level schema descriptions across all 44 tools.
- Dedicated, enforced output contracts for every MCP-visible tool, including
n8n_introspect. - Codex-compatible workflow node positions without weakening runtime validation.
- Stronger shared redaction, including secret-bearing object keys.
- Hardened release, artifact, consumer-resolution, and fork pull-request boundaries.
- 291 automated tests plus Linux, macOS, Windows, CodeQL, Semgrep, Trivy, Gitleaks, dependency, package, MCPB, and Registry gates.
Security note
The project and bundled MCPB dependency trees audit clean. A disposable downstream npm consumer still reports the tracked @hono/node-server advisory propagated by MCP SDK 1.29.0; that HTTP adapter is not loaded by this stdio-only server. The verifier accepts only the exact reviewed advisory chain or a fully clean transition and does not claim upstream closure prematurely.
See the frozen changelog entry for complete details.
v0.1.1
Documentation patch release. npm publication is now exclusively GitHub OIDC trusted publishing; documentation describes the published installation routes with the pinned exact-version npx quick start and progressive safety-mode framing. See CHANGELOG.md for details.
v0.1.0
Security-focused MCP server for self-hosted n8n Community Edition: 44 bounded tools, read-only by default, deterministic local Introspect engine, exact confirmation guards, and byte-reproducible artifacts. See CHANGELOG.md for the complete release notes.