Log inSubmit server
N8n MCP Community logo

N8n MCP Community

by drzamarian

Manage self-hosted n8n Community Edition workflows, executions, credentials, and tags through bounded MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install N8n MCP Community

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": {
    "drzamarian-n8n-mcp-community": {
      "command": "npx",
      "args": [
        "--yes",
        "n8n-mcp-community@latest"
      ],
      "env": {
        "N8N_API_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.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The drzamarian/n8n-mcp-community MCP server connects an MCP client to a self-hosted n8n Community Edition instance through its Public API. It exposes 44 bounded tools for inspecting and managing workflows, executions, credentials, tags, and related diagnostics, with read-only mode enabled by default. Write and unsafe modes gate mutations, deletions, activation, retries, stops, credential tests, and other higher-risk operations. Reach for it when an agent needs controlled access to n8n without sending data to an external AI service.

Use cases

  • Inspect accessible n8n workflows and their retained versions
  • Create or update workflows through controlled API mutations
  • Triage saved executions without exposing node payloads
  • Audit credential references before changing stored credentials
  • Organize workflows with reusable tags

Key features

  • 44 bounded MCP tools for n8n Community Edition
  • Read-only, write, and unsafe access modes
  • Workflow version comparison and guarded node edits
  • Value minimization for credentials, executions, and workflow data
  • Cursor-based bounded pagination
  • No external AI calls

Tools44

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

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

10/10 checks healthy over the last 60d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · n8n-mcp-community@latest (npm)

Adoption & maintenance

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

GitHub stars2Stargazers on the source repository.
npm downloads682Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed44Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How N8n MCP Community works

What drzamarian/n8n-mcp-community MCP server does

The drzamarian/n8n-mcp-community MCP server gives an MCP client a controlled interface to a self-hosted n8n Community Edition installation. Its tools cover workflow discovery and inspection, workflow creation and updates, node-level edits, activation and lifecycle changes, retained-version comparison, execution triage, credential metadata, credential schemas and usage, and workflow tags.

The server is designed around bounded operations. Listing tools return one API page and a continuation cursor rather than fetching every record automatically. Identifiers are validated according to their resource type, so a workflow ID, execution ID, credential ID, tag ID, and retained version ID cannot be substituted for one another. Responses omit sensitive values such as credential data, raw execution inputs and outputs, pinned workflow values, and static workflow values.

How it works

Communication uses MCP over the server's standard input and output. The server calls the configured n8n Public API using an API key and returns validated, value-minimized results to the client. It does not execute workflows itself and does not make external AI calls.

Three modes control access. Read-only mode exposes inspection and discovery operations. Write mode adds ordinary mutations such as creating workflows, updating selected fields, editing nodes, replacing tag assignments, and managing credentials or tags. Unsafe mode enables destructive actions and external-contact operations, including deletion, activation changes, execution retry or stop, credential testing, and archive operations. The n8n API key remains the upstream permission boundary, while the server mode is the server-side gate for unsafe tools.

Several writes include safeguards for n8n's API behavior. Workflow updates use an expected version identifier and are non-atomic full replacements; node edits require an explicit acknowledgement of residual race risk. Tag assignment replacement is a complete replacement rather than a merge, and execution cancellation reports whether n8n confirmed a stop or returned an ambiguous result.

Setup and configuration

The drzamarian/n8n-mcp-community MCP server requires Node.js 22 or 24, an n8n URL, and an n8n API key. Install the package globally with npm, or configure an MCP client to run it through npx. The client configuration supplies N8N_API_URL and N8N_API_KEY; N8N_MCP_MODE can select read-only, write, or unsafe, with read-only as the default.

Plain HTTP is accepted automatically only for loopback URLs. For a non-loopback HTTP n8n instance, set N8N_ALLOW_INSECURE_HTTP=1 to explicitly accept the risk of transmitting the API key and data without transport encryption. HTTPS is the appropriate choice when available.

Claude Desktop can also install the release MCPB without Node.js through its Extensions settings. Public builds should be obtained from npm or the project's GitHub releases. After configuration, restart the MCP client and verify that the expected tools are available.

Tools and capabilities

The main capability groups are:

  • List, inspect, create, update, archive, activate, deactivate, and delete workflows.
  • Edit one validated node property while preserving sibling data.
  • Retrieve retained workflow versions and compare them with current or historical states.
  • List, inspect, retry, stop, and delete saved executions without returning payload values.
  • Inspect credential schemas and metadata, create or update credentials, scan workflow usage, and optionally test a stored credential.
  • List and inspect reusable workflow tags, create tags, and replace a workflow's tag assignments.

Use discovery tools before mutation tools when an operation depends on a stable resource ID. Use workflow tag listing before replacing assignments if existing tags must be retained, and scan credential usage before changing or deleting a credential that workflows may reference.

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 Community

drzamarian/n8n-mcp-community is an MCP server that connects MCP clients to self-hosted n8n Community Edition through its Public API. Its 44 tools manage workflows, nodes, executions, credentials, and tags, while supporting version inspection, diagnostics, bounded pagination, and safety modes that limit writes and unsafe operations.

Install it globally with Node.js 22 or 24 using npm, or run it with npx from your MCP client configuration. Set N8N_API_URL and N8N_API_KEY, then optionally set N8N_MCP_MODE. Claude Desktop can instead install the released MCPB through its Extensions settings.

Yes, it works with Claude Desktop through a standard MCP configuration or the released MCPB package. The MCPB installation does not require Node.js; download it from a GitHub release, install it under Claude Desktop Extensions, and enter the n8n URL, API key, and mode.

It withholds credential values, raw execution inputs and outputs, pinned workflow values, and static workflow values from generic public tools. Read-only mode is the default, while write and unsafe operations require explicit mode selection and still depend on permissions granted to the n8n API key.

Set N8N_MCP_MODE to unsafe in the MCP client environment. This enables destructive and external-contact operations such as deletion, activation changes, execution retry or stop, and credential testing, but the n8n API key must also have the corresponding upstream permissions.

Related MCP servers

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