Skip to main content
mcpSource-backed
n8n-MCP logo

n8n MCP Server

MCP server that gives Claude and other MCP clients structured access to n8n node documentation, workflow templates, validation tools, and optional n8n API workflow management.

Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Brand
n8n-MCP
Brand domain
n8n-mcp.com
Brand asset source
brandfetch
Safety notes
The project explicitly warns users not to edit production n8n workflows directly with AI., Copy workflows, export backups, test in development, and validate every generated workflow before deploying., Optional n8n API tools can create, update, validate, and execute workflows; restrict them to non-production or tightly scoped accounts., Template-based workflow generation can still produce invalid credentials, missing defaults, or unsafe automations without human review.
Privacy notes
Workflow definitions can include business logic, customer data paths, webhook URLs, and credential names., n8n API credentials and hosted n8n-MCP API keys are secrets and should stay out of prompts, repository files, logs, and screenshots., Template searches, node lookups, validation payloads, and workflow metadata may be sent to the MCP server and the connected AI client.
Author
Romuald Czlonkowski
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/4 ready
Account & credentials2Install & runtime1Review & approval110 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.

4 areas
  • SafetyGeneralThe project explicitly warns users not to edit production n8n workflows directly with AI.
  • SafetyGeneralCopy workflows, export backups, test in development, and validate every generated workflow before deploying.
  • SafetyPermissions & scopesOptional n8n API tools can create, update, validate, and execute workflows; restrict them to non-production or tightly scoped accounts.
  • SafetyCredentials & tokensTemplate-based workflow generation can still produce invalid credentials, missing defaults, or unsafe automations without human review.
  • PrivacyCredentials & tokensWorkflow definitions can include business logic, customer data paths, webhook URLs, and credential names.
  • PrivacyCredentials & tokensn8n API credentials and hosted n8n-MCP API keys are secrets and should stay out of prompts, repository files, logs, and screenshots.
  • PrivacyThird-party handlingTemplate searches, node lookups, validation payloads, and workflow metadata may be sent to the MCP server and the connected AI client.

Safety notes

  • The project explicitly warns users not to edit production n8n workflows directly with AI.
  • Copy workflows, export backups, test in development, and validate every generated workflow before deploying.
  • Optional n8n API tools can create, update, validate, and execute workflows; restrict them to non-production or tightly scoped accounts.
  • Template-based workflow generation can still produce invalid credentials, missing defaults, or unsafe automations without human review.

Privacy notes

  • Workflow definitions can include business logic, customer data paths, webhook URLs, and credential names.
  • n8n API credentials and hosted n8n-MCP API keys are secrets and should stay out of prompts, repository files, logs, and screenshots.
  • Template searches, node lookups, validation payloads, and workflow metadata may be sent to the MCP server and the connected AI client.

Prerequisites

  • Node.js and npx, or a hosted n8n-MCP API key from the project dashboard.
  • MCP client such as Claude Code, Claude Desktop, Cursor, Windsurf, Codex, or VS Code.
  • n8n knowledge sufficient to review generated workflows before deployment.
  • Optional n8n API credentials if enabling direct workflow create, update, or execution tools.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "n8n-mcp"]
    }
  }
}

About this resource

Content

n8n-MCP gives MCP clients structured access to n8n node metadata, documentation, examples, workflow templates, validation helpers, and optional n8n API operations. It is designed for AI-assisted workflow authoring across Claude Code, Claude Desktop, Cursor, Windsurf, Codex, VS Code, and other MCP clients.

The project documents more than 1,800 n8n nodes, thousands of workflow templates, and validation tools for checking node configuration and full workflow structure before deployment.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository and project docs for current install commands, hosted quotas, n8n version support, tool coverage, and deployment guidance.

Features

  • Search n8n node metadata, operations, properties, and AI-capable node variants.
  • Search and inspect workflow templates before building from scratch.
  • Retrieve node documentation in minimal, standard, full, property-search, or docs-focused modes.
  • Validate node configs and full workflows before deployment.
  • Optionally create, update, test, and inspect workflows through the n8n API.
  • Run as a local npx server, Docker deployment, Railway deployment, or hosted dashboard-backed MCP server.
  • Use real examples from workflow templates to improve node configuration.

Installation

For a basic local Claude Code setup:

claude mcp add n8n-mcp -- npx -y n8n-mcp

For clients that use JSON configuration:

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "n8n-mcp"]
    }
  }
}

Use the project documentation for hosted dashboard setup, Docker deployment, Railway deployment, and optional n8n API access.

Use Cases

  • Find the right n8n node and operation for a workflow step.
  • Convert an automation requirement into a validated n8n workflow draft.
  • Search existing templates before generating a workflow from scratch.
  • Validate node parameters, expressions, and workflow wiring before import.
  • Review n8n AI nodes and tool variants while designing agentic workflows.
  • Safely test workflow edits in a development n8n instance before production.

Safety and Privacy

Do not connect n8n-MCP directly to production workflow management without guardrails. Work from copies, export backups, use development environments, and require human approval before activating or deploying generated workflows.

Workflow JSON may reveal webhooks, system integrations, credential labels, business process logic, and customer data paths. Keep n8n API keys and hosted n8n-MCP API keys in secret storage, not in prompts or repository files.

Duplicate Check

content/tools/n8n.mdx covers n8n as a workflow automation tool. This entry is for the separate czlonkowski/n8n-mcp MCP server and belongs in content/mcp.

Source citations

Add this badge to your README

Show that n8n MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/n8n-mcp.svg)](https://heyclau.de/entry/mcp/n8n-mcp)

How it compares

n8n MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field

MCP server that gives Claude and other MCP clients structured access to n8n node documentation, workflow templates, validation tools, and optional n8n API workflow management.

Open dossier

Official AWS Labs fully-managed remote MCP server providing up-to-date AWS documentation, code samples, agent skills, API and CloudFormation regional availability, and CDK/Amplify/Strands guidance over a hosted HTTP endpoint.

Open dossier

Browse, summarize, and generate Canva designs directly from Claude

Open dossier

Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustDiffersPackage not verifiedPackage not verifiedPackage verifiedPackage not verified
Source provenanceDiffersSource-backedSource-backedNo submission linkSource-backed
SubmitterDiffersoktofeesh1jaso0n0818glorydavid03023
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brandn8n-MCP logon8n-MCPAWS Labs logoAWS LabsCanva logoCanva
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedFirst-partySource-backed
AuthorRomuald CzlonkowskiAWS LabsCanvaUpstash
Added2026-06-052026-06-212025-09-182026-06-02
Platforms
Harness
Source repo
Safety notesThe project explicitly warns users not to edit production n8n workflows directly with AI. Copy workflows, export backups, test in development, and validate every generated workflow before deploying. Optional n8n API tools can create, update, validate, and execute workflows; restrict them to non-production or tightly scoped accounts. Template-based workflow generation can still produce invalid credentials, missing defaults, or unsafe automations without human review.This is a fully managed remote server hosted by AWS; it serves public AWS knowledge and requires no AWS account or credentials, so do not add AWS access keys for it. Because it is a remote server, your queries are sent to the AWS-hosted endpoint; only connect clients you trust to route requests there. Generative output about AWS APIs and resources can still be wrong; verify guidance against the official AWS documentation it links.Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation. Returned documentation and code snippets are third-party content; review examples before running them in your project.
Privacy notesWorkflow definitions can include business logic, customer data paths, webhook URLs, and credential names. n8n API credentials and hosted n8n-MCP API keys are secrets and should stay out of prompts, repository files, logs, and screenshots. Template searches, node lookups, validation payloads, and workflow metadata may be sent to the MCP server and the connected AI client.Your documentation queries and search terms are sent over HTTPS to the AWS-hosted knowledge endpoint to retrieve content. The server returns public AWS documentation, code samples, and availability data; it does not read any private account data.Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.The library names and documentation topics you query are sent to the Context7 service to return matching docs. Avoid placing secrets or private identifiers in the library queries passed to the server.
Prerequisites
  • Node.js and npx, or a hosted n8n-MCP API key from the project dashboard.
  • MCP client such as Claude Code, Claude Desktop, Cursor, Windsurf, Codex, or VS Code.
  • n8n knowledge sufficient to review generated workflows before deployment.
  • Optional n8n API credentials if enabling direct workflow create, update, or execution tools.
  • An MCP client that supports remote HTTP MCP servers (or `uvx`/`fastmcp` to proxy the endpoint to stdio for clients that don't).
  • Outbound HTTPS access to the hosted endpoint `https://knowledge-mcp.global.api.aws`.
  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • Node.js 18+ and npx available (verify with: npx --version)
  • Claude Code or Claude Desktop with MCP support
  • Internet access so the server can reach the Context7 documentation service
  • Optional Context7 API key for higher rate limits; the server also works without one
Install
claude mcp add n8n-mcp -- npx -y n8n-mcp
uvx fastmcp run https://knowledge-mcp.global.api.aws
claude mcp list && claude mcp status canva
claude mcp add context7 -- npx -y @upstash/context7-mcp
Config
{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "n8n-mcp"]
    }
  }
}
{
  "mcpServers": {
    "aws-knowledge-mcp-server": {
      "url": "https://knowledge-mcp.global.api.aws",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "canva": {
      "url": "https://mcp.canva.com/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.