← Back to directory
N

n8n MCP Server

Community
Help AI assistants understand and build n8n workflows.
Category
Dev Tools #147 of 438
Stars
★ 23.1k Very popular
Runtime
Node.js · Docker · Hosted (no local runtime)
Credentials
Optional API key
License
MIT
Last commit
Tools
24
58FMRS · C

The source identifies czlonkowski/n8n as the repository and maintainer, with an MIT license and the repository root as the server path. The server manifest is not cached, and the README does not specify a transport protocol or complete client installation configuration.

Strongest · Documentation 14/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
12/20
Maintenance
13/20
Documentation
14/20
Setup experience
11/20
Why each score
Reliability 8/20
The README lists a substantial tool surface, validation workflow, and several deployment paths, but the server manifest is unavailable and no verifiable source, CI workflow, or committed test files are supplied. The “5418 passing” badge is not execution evidence under this review. The happy path is plausible, but initialization handshake behavior, declaration consistency, dependency control, and error handling cannot be confirmed, so the static calibration requires a deduction.
Security and permissions 12/20
The README identifies API-key and Cloudflare credential environment variables and states that Cloudflare credentials are confined to the N8N_API_URL origin. It also documents disabling write, delete, test, credential, and data-table tools, plus blocking destructive operations within bundled tools. These are meaningful permission and data-boundary controls. However, high-impact workflow, credential, data-table, execution, and deletion tools remain available, and there is no source-level evidence of default confirmation, complete data-flow controls, or authorization enforcement, so this is not near full marks.
Maintenance 13/20
The project states an MIT license, is not archived, and provides a changelog, contribution guide, sponsorship channel, and explicit n8n version information, giving reasonable ownership and maintenance signals. The supplied material does not provide verifiable release history, commit cadence, dependency-update practice, vulnerability-response channel, or issue-response evidence. Stars and open issues are discovery signals only and add no points.
Documentation 14/20
The README covers self-hosting, Docker, Railway, cloud deployment, n8n integration, Cloudflare authentication, security hardening, privacy telemetry, HTTP deployment, workflow diffs, and client integrations. It also describes the tools and their main modes, making the documentation structure strong. Points are deducted because the linked documentation contents are not supplied, the manifest is missing, and costs, limits, troubleshooting, and declared behavior cannot be independently reviewed; the README is also untrusted evidence.
Setup experience 11/20
The README offers a hosted dashboard, a stated free quota, self-hosting options, and setup-document links for several mainstream clients and platforms. The actual installation commands, client configuration examples, runtime prerequisites, and server manifest are not provided, so the complete path from environment preparation to a verified MCP connection cannot be established. This supports a usable but manual and incompletely evidenced setup score.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Developers building n8n automation with Claude, Cursor, Windsurf, VS Code, Codex, or Antigravity.
  • n8n users who need node documentation, template discovery, and workflow validation.
  • Teams that want to self-host n8n-MCP or use it through the hosted dashboard.

Not for

  • Automation scenarios that do not use n8n.
  • Users who need n8n instance management without configuring the n8n API.
  • Production workflow changes made without testing.

Required permissions

  • Permissions required for basic node, documentation, template, and validation features are not specified in the source.
  • n8n management features require N8N_API_URL and N8N_API_KEY.
  • Credential and data-table tools may access sensitive n8n data; the source recommends disabling them in governance-sensitive environments.

Risks and side effects

  • AI-generated results may be unpredictable; the source explicitly warns against editing production workflows directly.
  • Copy workflows, test in development, back up important workflows, and validate changes before deployment.
  • Enabling workflow write, delete, credential, or data-table management increases potential impact.

Setup

Before you start

Runtime:Node.js · Docker · Hosted (no local runtime)

N8N_API_KEY optionalsecret API key generated in your n8n instance (Settings → API), used together with N8N_API_URL.
N8N_CF_CLIENT_SECRET optionalsecret Cloudflare Access service token Client Secret used to authenticate n8n API requests.
Other optional settings (4)
N8N_API_URL optional Base URL of your n8n instance API; required to use the n8n management tools.
N8N_CF_CLIENT_ID optional Cloudflare Access service token Client ID, needed when your n8n sits behind Cloudflare Zero Trust.
DISABLED_TOOLS optional Comma-separated list of tools to disable entirely, for read-only deployments.
DISABLED_TOOL_OPERATIONS optional Finer-grained control to block specific destructive operations (e.g. delete, run) within tools.

Register at dashboard.n8n-mcp.com to obtain an API key and connect an MCP client, or follow the repository's self-hosting guide using npx, Docker, Railway, or local installation. To connect an n8n instance, configure N8N_API_URL and N8N_API_KEY. If the instance is behind Cloudflare Access, N8N_CF_CLIENT_ID and N8N_CF_CLIENT_SECRET can also be configured.

Check that it works

After connecting, search_nodes and tools_documentation should appear in your client's tool list; call n8n_health_check to confirm n8n API connectivity, or ask it to search for webhook-related nodes to prove the server is working.

Troubleshooting

  1. Check that N8N_API_URL and N8N_API_KEY are configured correctly.
  2. Use n8n_health_check to check API connectivity and features.
  3. For n8n instances behind Cloudflare Access, check N8N_CF_CLIENT_ID and N8N_CF_CLIENT_SECRET.
  4. Consult the repository's self-hosting, HTTP deployment, and n8n deployment guides.

Things to try

Once connected, you can ask your AI assistant things like:

  • Search n8n workflow templates for Slack notifications
  • Show me the configuration properties of the n8n-nodes-base.webhook node
  • Validate this workflow's node configs and connections before I deploy it
  • List recent failed executions from my n8n instance

Tools 24

tools_documentation read-only
Get documentation for MCP tools.
search_nodes read-only
Search n8n nodes with optional configuration examples.
get_node read-only
Get node information, documentation, properties, versions, or migration details.
validate_node read-only
Validate a node configuration.
validate_workflow read-only
Validate a complete n8n workflow.
search_templates read-only
Search n8n workflow templates.
get_template read-only
Retrieve template workflow content.
n8n_create_workflow writes
Create an n8n workflow.
Show 16 more tools
n8n_get_workflow read-only
Retrieve an n8n workflow.
n8n_update_full_workflow writes
Replace an n8n workflow completely.
n8n_update_partial_workflow writes
Update an n8n workflow using diff operations.
n8n_delete_workflow destructive
Permanently delete an n8n workflow.
n8n_list_workflows read-only
List and filter n8n workflows.
n8n_validate_workflow read-only
Validate a workflow in n8n by ID.
n8n_autofix_workflow writes
Automatically fix common workflow errors.
n8n_workflow_versions writes
Manage workflow version history and rollbacks.
n8n_deploy_template writes
Deploy an n8n.io template to an n8n instance.
n8n_test_workflow writes
Test or trigger a workflow execution.
n8n_executions writes
Manage workflow executions.
n8n_evaluations writes
Read n8n evaluation test runs and metrics.
n8n_manage_datatable writes
Manage n8n data tables and rows.
n8n_manage_credentials writes
Manage n8n credentials.
n8n_audit_instance read-only
Perform a security audit of an n8n instance.
n8n_health_check read-only
Check n8n API connectivity and features.

Use cases

Search n8n nodes, properties, and official documentation.
Design and validate n8n workflows from templates or from scratch.
Create, update, test, and audit workflows after configuring the n8n API.

Supported clients

Claude Desktop
Claude Code
Windsurf
Cursor
VS Code
Codex
Antigravity

Listed from the project's documentation, not tested by this site.

Overview

n8n-MCP is a Model Context Protocol server that gives AI assistants access to n8n node documentation, properties, operations, templates, and workflow validation. It supports searching and configuring core and community nodes, and can manage workflows, executions, credentials, and data tables when the n8n API is configured.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →

Source revision 26d79a47fa33 Data synced 2026-10-19 Read the FMRS scoring method