Log inSubmit server
MCP N8n logo

MCP N8n

Operate n8n workflows, executions, credentials, projects, and administration through 61 MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP N8n

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-n8n"
      ],
      "env": {
        "N8N_BASE_URL": "YOUR_VALUE_HERE",
        "N8N_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 61 tools correctly (8d ago).

Overview

The mcp-n8n MCP server connects AI clients to an n8n instance through its API, supporting workflow administration and construction. It provides a 560-node catalog with schemas, validation, autofix, snapshots, rollback, execution debugging, backups, and health reports. Run it locally over stdio or expose it over streamable HTTP for remote clients. Reach for it when an agent needs to build, inspect, test, repair, or administer n8n workflows.

Use cases

  • Build n8n workflows from natural-language requirements
  • Validate and repair workflows before activation
  • Debug failed executions at the node level
  • Back up, compare, and roll back workflow changes
  • Administer n8n projects, users, credentials, and executions

Key features

  • 560-node catalog with parameter schemas
  • Workflow validation and automatic repair
  • Snapshots, rollback, diff, and full-instance backup
  • Execution monitoring and per-node debugging
  • n8n.io and bundled template search
  • Local stdio and remote streamable HTTP modes

Tools61

What MCP N8n lets your agent do. Expand a tool for its parameters.

Verified live~6.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 41d

What it can do

From the 61 tools this server returned when we ran it; 34 declare their own safety hints.

Can delete or modify data · 8Handles credentials · 9Makes network requests · 3Read-only tools · 53
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age351 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · mcp-n8n (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars21Stargazers on the source repository.
npm downloads893Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed61Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP N8n works

What mcp-n8n does

The mcp-n8n MCP server gives an AI client access to n8n operations through the n8n API. It covers workflow creation, retrieval, updates, deletion, activation, project transfers, and tags. It also exposes execution monitoring, retries, execution-history cleanup, credential creation and schema discovery, variables, projects, users, permissions, and audit logs.

For workflow construction, mcp-n8n includes a catalog of 560 nodes gathered from n8n packages. Node entries include parameter types, allowed values, display conditions, credential information, and current type versions. Agents can search the catalog, inspect node definitions, validate workflows, repair common structural problems, and make partial edits without replacing the entire workflow.

How it works

The server communicates with an n8n instance using the base URL and an API key. It normally runs as a local stdio process, but it can also serve MCP over streamable HTTP. HTTP mode includes a health endpoint and can require a bearer token for incoming requests.

Validation checks node types, required parameters, conditional requirements, option values, type versions, connections, and selected expression errors before a workflow is saved or activated. The autofix operation can add missing positions or type versions, rename duplicates, repair dangling connections, and correct expression prefixes. Agents can preview changes before applying them.

The server creates a local snapshot before updates, partial edits, autofixes, and deletions. Snapshots support rollback and comparison with the current workflow. A deleted workflow can be recreated from a snapshot when requested. Webhook-trigger workflows can also be called for end-to-end testing, returning the actual HTTP response.

Setup and configuration

Install the package globally with npm or run it through npx. Configure N8N_BASE_URL with the n8n instance address and N8N_API_KEY with an API key generated in n8n settings. N8N_TOOLSETS is optional and defaults to all; core,builder limits the available areas, while admin selects administration tools.

Set N8N_MCP_HTTP_PORT to enable streamable HTTP instead of the default local stdio mode. Set N8N_MCP_HTTP_TOKEN to require Authorization: Bearer authentication for HTTP requests. Snapshot storage defaults to ~/.mcp-n8n/snapshots and can be changed with N8N_SNAPSHOT_DIR. Docker usage can mount /data to persist snapshots between runs.

Cursor uses an npx-based configuration in the supplied example. No hosted account is required for the MCP server itself, but it does need access to a configured n8n instance.

Tools and capabilities

The mcp-n8n MCP server includes tools for:

  • Listing, creating, updating, activating, deleting, tagging, and transferring workflows.
  • Searching and inspecting nodes, importing public n8n.io templates, and using bundled templates.
  • Validating, autofixing, partially editing, and testing workflows.
  • Inspecting node-level execution data and diagnosing the latest error.
  • Calculating workflow health from recent executions, including success rates, failures, duration, and last failure.
  • Exporting all workflows to JSON files and importing them later.
  • Managing credentials, variables, projects, users, permissions, and audit records.

The package also provides build-workflow and fix-workflow MCP prompts that guide an agent through construction, validation, testing, and repair. Listing supports a summary endpoint, field filtering, smaller default result sets, and warnings for operations likely to consume many tokens.

Limitations and notes

The server operates against the n8n instance available through the configured API credentials; its access therefore depends on that instance and the permissions of the key. HTTP authentication is optional in configuration but is recommended when exposing the server remotely. The node catalog is regenerated weekly by CI, so its schemas represent the generated catalog rather than an independently maintained list. Snapshot files and exported workflow JSON require suitable local or mounted storage.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP N8n

mcp-n8n is an MCP server that connects AI clients to an n8n instance through its API. Its main tools manage workflows, executions, credentials, projects, users, and audit data, while builder tools search node schemas, validate and repair workflows, create snapshots, roll back changes, and test webhook-triggered flows.

Install it globally with `npm install -g mcp-n8n` or run it with `npx -y mcp-n8n`. Configure `N8N_BASE_URL` and `N8N_API_KEY` in the MCP client environment, then restart Claude Desktop or Cursor.

Yes, mcp-n8n works with Cursor through its MCP settings. The documented configuration uses `npx -y mcp-n8n` and passes `N8N_BASE_URL` and `N8N_API_KEY` as environment variables.

Yes, set `N8N_MCP_HTTP_PORT` to expose streamable HTTP instead of local stdio. You can set `N8N_MCP_HTTP_TOKEN` so requests must include a bearer token, and clients that support streamable HTTP can connect to the configured endpoint.

mcp-n8n saves local snapshots before updates, partial edits, autofixes, and deletions, then provides rollback and snapshot diff tools. It can also export every workflow as JSON and import those files to restore workflows.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP N8n AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-n8n?style=directory)](https://allmcps.com/mcp/mcp-n8n)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-n8n"><img src="https://allmcps.com/api/badge/mcp-n8n?style=directory" alt="MCP N8n on AllMCPs" /></a>