Log inSubmit server
N8n MCP logo

N8n MCP

by AutomateLab-tech

Generates, audits, diffs, and deploys n8n workflows through MCP, with execution diagnosis and replay tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install N8n MCP

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": {
    "automatelab-tech-n8n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@automatelab/n8n-mcp"
      ],
      "env": {
        "N8N_API_URL": "YOUR_VALUE_HERE",
        "N8N_API_KEY": "YOUR_VALUE_HERE",
        "N8N_MCP_READ_ONLY": "YOUR_VALUE_HERE",
        "N8N_MCP_DISABLED_TOOLS": "YOUR_VALUE_HERE",
        "N8N_MCP_ALLOWED_WORKFLOW_IDS": "YOUR_VALUE_HERE",
        "N8N_MCP_ALLOWED_TAGS": "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 12 tools correctly ().

Overview

AutomateLab-tech/n8n-mcp MCP server connects AI agents to n8n for workflow generation, linting, execution diagnosis, semantic diffing, and live-instance management. Stateless tools accept workflow or execution JSON, while live tools use the n8n API to list, retrieve, create, activate, and inspect workflows and executions. Reach for it when an agent needs to produce importable n8n JSON, catch configuration problems, investigate dropped items, or manage workflows through a configured n8n instance. It also includes a TypeScript custom-node scaffold tool and a Claude Code skill.

Use cases

  • Generate an n8n workflow from a plain-English description
  • Lint workflow JSON before importing it into n8n
  • Diagnose an execution where items disappear between nodes
  • Compare a deployed workflow with a local version
  • Create and activate workflows through the n8n API

Key features

  • Natural-language workflow generation
  • Deterministic workflow linting
  • Semantic workflow diffs
  • Per-node execution diagnosis and timelines
  • Single-node execution replay
  • Live n8n workflow and execution management

Tools12

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

Verified live~2.3k 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

Recent health check succeeded.

22/22 checks healthy over the last 95d

What it can do

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

Runs commands · 1Handles credentials · 4Makes network requests · 7Read-only tools · 11
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age185 days
Maintainers1

Observed 2026-11-11 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 9d ago via OSV.dev · @automatelab/n8n-mcp (npm)

Adoption & maintenance

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

GitHub stars14Stargazers on the source repository.
npm downloads369Package downloads in the last 30 days.
Last commit22d 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 exposed12Callable tools this server registers over MCP.
Directory activity9 viewsConfig copies, upvotes, and views on AllMCPs.

How N8n MCP works

What AutomateLab-tech/n8n-mcp MCP server does

AutomateLab-tech/n8n-mcp MCP server exposes n8n-focused tools for both workflow authoring and operational debugging. The stateless tools work from JSON or plain-language descriptions without connecting to an n8n instance. They can generate workflows, scaffold custom nodes, lint configurations, compare workflow versions, explain failed executions, create single-node replay workflows, and render execution timelines.

The generator handles webhook, schedule, and RSS triggers; common actions such as Slack, Google Sheets, Discord, Gmail, Notion, and HTTP; and AI Agent arrangements using LangChain model, memory, and tool connections. Generated workflow JSON includes node IDs, positions, connections, and node type versions. The custom-node tool returns one TypeScript file containing an INodeType implementation skeleton.

How it works

MCP clients call the exposed tools over the server's standard MCP interface. Rule-based analysis tools return structured findings rather than changing input data. workflow_lint checks issues such as deprecated node types, missing or invalid typeVersion values, broken connections, stale expressions, credential drift, unsafe Code-node patterns, and AI Agent wiring problems. workflow_diff compares nodes, fields, connections, and settings while ignoring small positional changes and timestamp noise.

For execution troubleshooting, execution_explain accepts execution data from the n8n interface or API and identifies empty outputs, unresolved expressions, node errors, hints, and token usage. execution_timeline presents timing and item counts in a markdown table. execution_replay builds a Manual Trigger to Code seed to target-node workflow, using supplied input items or execution data.

The live REST tools use N8N_API_URL and N8N_API_KEY. They list or fetch workflows, create inactive workflows, change activation state, and list executions with optional full execution data. A typical workflow is to generate or retrieve JSON, lint it, create it in n8n, and activate it separately.

Setup and configuration

AutomateLab-tech/n8n-mcp MCP server requires Node.js 20 or later. Install it with npx -y @automatelab/n8n-mcp in an MCP host configuration, or install the package globally with npm. N8N_API_URL and N8N_API_KEY are optional for the stateless tools but required for live-instance operations. The API key is created in n8n under Settings, API, and Create API key.

Runtime policies can restrict access without changing the source. N8N_MCP_READ_ONLY=1 disables workflow creation, activation, and node scaffolding. N8N_MCP_DISABLED_TOOLS prevents selected tools from registering, while N8N_MCP_ALLOWED_WORKFLOW_IDS and N8N_MCP_ALLOWED_TAGS constrain live workflow access. The repository also documents Docker, Render, Railway, Fly.io, Claude Desktop bundle, and GitHub Action deployment options.

Tools and capabilities

  • Generate workflow JSON from natural-language requirements.
  • Scaffold an n8n custom node in TypeScript.
  • Lint workflows with deterministic errors and warnings.
  • Compare workflow structure and settings semantically.
  • Explain failures and render execution timelines.
  • Build isolated replay workflows for individual nodes.
  • List, retrieve, create, activate, and inspect workflows and executions on a live n8n instance.

Limitations and notes

The live tools need a reachable n8n API and valid credentials; the stateless tools do not. Workflow generation is non-deterministic because it creates random node IDs and webhook paths. Creating a workflow does not activate it, and execution_list can return a large payload when includeData is enabled. AutomateLab-tech/n8n-mcp is best suited to the Developer Tools category when an agent needs n8n-specific validation and debugging rather than a complete indexed catalog of every n8n node.

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 N8n MCP

AutomateLab-tech/n8n-mcp is an MCP server that connects AI agents to n8n. Its main tools generate workflow JSON, scaffold custom nodes, lint and compare workflows, explain executions, build node replays, render timelines, and manage workflows and executions through the n8n API when configured.

Install it by running `npx -y @automatelab/n8n-mcp` from your MCP client configuration, or install it globally with `npm install -g @automatelab/n8n-mcp`. Node.js 20 or later is required.

Yes, AutomateLab-tech/n8n-mcp works with Cursor through its MCP configuration. Add the server command and package arguments to Cursor's `~/.cursor/mcp.json`; add the n8n API environment variables if live-instance tools are needed.

No, API credentials are not needed for the stateless tools. Set `N8N_API_URL` and `N8N_API_KEY` to use workflow listing, retrieval, creation, activation, and live execution queries against an n8n instance.

Use `execution_explain` with execution JSON from n8n's Show details view or the executions API. It reports empty node outputs, unresolved expressions, errors with hints, and token usage; use `execution_timeline` when you also need per-node timing.

Related MCP servers

All in Communication 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 PreviewN8n MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/automatelab-tech-n8n-mcp?style=directory)](https://allmcps.com/mcp/automatelab-tech-n8n-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/automatelab-tech-n8n-mcp"><img src="https://allmcps.com/api/badge/automatelab-tech-n8n-mcp?style=directory" alt="N8n MCP on AllMCPs" /></a>