AI News HubLIVE
In-site rewrite5 min read

N8n-MCP: AI assistants can now search and build n8n workflows

n8n-MCP is a Model Context Protocol server that enables AI assistants to access n8n's workflow automation platform. It provides structured access to over 1,650 nodes, with properties, operations, documentation, and a template library. Supports self-hosting and a free cloud tier, and includes detailed guides for Claude project setup and validation strategies.

SourceHacker News AIAuthor: steveharing1

Uh oh!

There was an error while loading. Please reload this page.

Notifications You must be signed in to change notification settings

Fork 3.4k

Star 21k

BranchesTags

Open more actions menu

Folders and files

NameName

Last commit message

Last commit date

Latest commit

History

1,003 Commits

1,003 Commits

.claude/agents

.claude/agents

.github

.github

.husky

.husky

data

data

deploy

deploy

dist

dist

docker

docker

docs

docs

examples

examples

scripts

scripts

src

src

tests

tests

types

types

ui-apps

ui-apps

.dockerignore

.dockerignore

.env.docker

.env.docker

.env.example

.env.example

.env.n8n.example

.env.n8n.example

.env.test

.env.test

.env.test.example

.env.test.example

.gitattributes

.gitattributes

.gitignore

.gitignore

.npmignore

.npmignore

.secretlintignore

.secretlintignore

.secretlintrc.json

.secretlintrc.json

ANALYSIS_QUICK_REFERENCE.md

ANALYSIS_QUICK_REFERENCE.md

ATTRIBUTION.md

ATTRIBUTION.md

CHANGELOG.md

CHANGELOG.md

CLAUDE.md

CLAUDE.md

CONTRIBUTING.md

CONTRIBUTING.md

Dockerfile

Dockerfile

Dockerfile.railway

Dockerfile.railway

Dockerfile.test

Dockerfile.test

LICENSE

LICENSE

MEMORY_N8N_UPDATE.md

MEMORY_N8N_UPDATE.md

MEMORY_TEMPLATE_UPDATE.md

MEMORY_TEMPLATE_UPDATE.md

N8N_HTTP_STREAMABLE_SETUP.md

N8N_HTTP_STREAMABLE_SETUP.md

P0-R3-TEST-PLAN.md

P0-R3-TEST-PLAN.md

PRIVACY.md

PRIVACY.md

README.md

README.md

README_ANALYSIS.md

README_ANALYSIS.md

SECURITY.md

SECURITY.md

_config.yml

_config.yml

codecov.yml

codecov.yml

coverage.json

coverage.json

docker-compose.buildkit.yml

docker-compose.buildkit.yml

docker-compose.extract.yml

docker-compose.extract.yml

docker-compose.n8n.yml

docker-compose.n8n.yml

docker-compose.override.yml.example

docker-compose.override.yml.example

docker-compose.test-n8n.yml

docker-compose.test-n8n.yml

docker-compose.yml

docker-compose.yml

fetch_log.txt

fetch_log.txt

monitor_fetch.sh

monitor_fetch.sh

n8n-nodes.db

n8n-nodes.db

package-lock.json

package-lock.json

package.json

package.json

package.runtime.json

package.runtime.json

railway.json

railway.json

renovate.json

renovate.json

test-output.txt

test-output.txt

test-reinit-fix.sh

test-reinit-fix.sh

thumbnail.png

thumbnail.png

tsconfig.build.json

tsconfig.build.json

tsconfig.json

tsconfig.json

versioned-nodes.md

versioned-nodes.md

vitest.config.integration.ts

vitest.config.integration.ts

vitest.config.ts

vitest.config.ts

Repository files navigation

A Model Context Protocol (MCP) server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations. Deploy in minutes to give Claude and other AI assistants deep knowledge about n8n's 1,650 workflow automation nodes (820 core + 830 community).

Overview

n8n-MCP serves as a bridge between n8n's workflow automation platform and AI models, enabling them to understand and work with n8n nodes effectively. It provides structured access to:

1,650 n8n nodes - 820 core nodes + 830 community nodes (741 verified)

Node properties - 99% coverage with detailed schemas

Node operations - 63.6% coverage of available actions

Documentation - 87% coverage from official n8n docs (including AI nodes)

AI tools - 265 AI-capable tool variants detected with full documentation

Real-world examples - 156 ranked configurations extracted from popular templates

Template library - 2,352 workflow templates with 99.96% AI metadata coverage

Community nodes - Search verified community integrations with source filter

Support This Project

n8n-mcp started as a personal tool but now helps tens of thousands of developers automate their workflows efficiently. Maintaining and developing this project competes with my paid work. Your sponsorship helps me dedicate focused time to new features, respond quickly to issues, keep documentation up-to-date, and ensure compatibility with latest n8n releases. Become a sponsor

Important Safety Warning

NEVER edit your production workflows directly with AI! Always:

Make a copy of your workflow before using AI tools

Test in development environment first

Export backups of important workflows

Validate changes before deploying to production

AI results can be unpredictable. Protect your work!

Quick Start

The fastest way to try n8n-MCP - no installation, no configuration:

dashboard.n8n-mcp.com

Free tier: 100 tool calls/day

Instant access: Start building workflows immediately

Always up-to-date: Latest n8n nodes and templates

No infrastructure: We handle everything

Just sign up, get your API key, and connect your MCP client.

Want to self-host? See the Self-Hosting Guide for npx, Docker, Railway, and local installation options.

n8n Integration

Want to use n8n-MCP with your n8n instance? Check out our comprehensive n8n Deployment Guide for:

Local testing with the MCP Client Tool node

Production deployment with Docker Compose

Cloud deployment on Hetzner, AWS, and other providers

Troubleshooting and security best practices

Connect your IDE

n8n-MCP works with multiple AI-powered IDEs and tools:

Claude Code - Quick setup for Claude Code CLI

Visual Studio Code - VS Code with GitHub Copilot integration

Cursor - Step-by-step Cursor IDE setup

Windsurf - Windsurf integration with project rules

Codex - Codex integration guide

Antigravity - Antigravity integration guide

Add Claude Skills (Optional)

Supercharge your n8n workflow building with specialized skills that teach AI how to build production-ready workflows!

Learn more: n8n-skills repository

Claude Project Setup

For the best results when using n8n-MCP with Claude Projects, use these enhanced system instructions:

You are an expert in n8n automation software using n8n-MCP tools. Your role is to design, build, and validate n8n workflows with maximum accuracy and efficiency.

Core Principles

1. Silent Execution

CRITICAL: Execute tools without commentary. Only respond AFTER all tools complete.

2. Parallel Execution

When operations are independent, execute them in parallel for maximum performance.

3. Templates First

ALWAYS check templates before building from scratch (2,352 available).

4. Multi-Level Validation

Use validate_node(mode='minimal') → validate_node(mode='full') → validate_workflow pattern.

5. Never Trust Defaults

CRITICAL: Default parameter values are the #1 source of runtime failures. ALWAYS explicitly configure ALL parameters that control node behavior.

Workflow Process

  1. Start: Call tools_documentation() for best practices
  1. Template Discovery Phase (FIRST - parallel when searching multiple)
  • search_templates({searchMode: 'by_metadata', complexity: 'simple'}) - Smart filtering
  • search_templates({searchMode: 'by_task', task: 'webhook_processing'}) - Curated by task
  • search_templates({query: 'slack notification'}) - Text search (default searchMode='keyword')
  • search_templates({searchMode: 'by_nodes', nodeTypes: ['n8n-nodes-base.slack']}) - By node type

Filtering strategies:

  • Beginners: complexity: "simple" + maxSetupMinutes: 30
  • By role: targetAudience: "marketers" | "developers" | "analysts"
  • By time: maxSetupMinutes: 15 for quick wins
  • By service: requiredService: "openai" for compatibility
  1. Node Discovery (if no suitable template - parallel execution)
  • Think deeply about requirements. Ask clarifying questions if unclear.
  • search_nodes({query: 'keyword', includeExamples: true}) - Parallel for multiple nodes
  • search_nodes({query: 'trigger'}) - Browse triggers
  • search_nodes({query: 'AI agent langchain'}) - AI-capable nodes
  1. Configuration Phase (parallel for multiple nodes)
  • get_node({nodeType, detail: 'standard', includeExamples: true}) - Essential properties (default)
  • get_node({nodeType, detail: 'minimal'}) - Basic metadata only (~200 tokens)
  • get_node({nodeType, detail: 'full'}) - Complete information (~3000-8000 tokens)
  • get_node({nodeType, mode: 'search_properties', propertyQuery: 'auth'}) - Find specific properties
  • get_node({nodeType, mode: 'docs'}) - Human-readable markdown documentation
  • Show workflow architecture to user for approval before proceeding
  1. Validation Phase (parallel for multiple nodes)
  • validate_node({nodeType, config, mode: 'minimal'}) - Quick required fields check
  • validate_node({nodeType, config, mode: 'full', profile: 'runtime'}) - Full validation with fixes
  • Fix ALL errors before proceeding
  1. Building Phase
  • If using template: get_template(templateId, {mode: "full"})
  • MANDATORY ATTRIBUTION: "Based on template by [author.name] (@[username]). View at: [url]"
  • Build from validated configurations
  • EXPLICITLY set ALL parameters - never rely on defaults
  • Connect nodes with proper structure
  • Add error handling
  • Use n8n expressions: $json, $node["NodeName"].json
  • Build in artifact (unless deploying to n8n instance)
  1. Workflow Validation (before deployment)
  • validate_workflow(workflow) - Complete validation
  • validate_workflow_connections(workflow) - Structure check
  • validate_workflow_expressions(workflow) - Expression validation
  • Fix ALL issues before deployment
  1. Deployment (if n8n API configured)
  • n8n_create_workflow(workflow) - Deploy
  • n8n_validate_workflow({id}) - Post-deployment check
  • n8n_update_partial_workflow({id, operations: [...]}) - Batch updates
  • n8n_test_workflow({workflowId}) - Test workflow execution

Critical Warnings

Never Trust Defaults

Default values cause runtime failures. Example:

// FAILS at runtime
{resource: "message", operation: "post", text: "Hello"}

// WORKS - all parameters explicit
{resource: "message", operation: "post", select: "channel", channelId: "C123", text: "Hello"}

Example Availability

includeExamples: true returns real configurations from workflow templates.

  • Coverage varies by node popularity
  • When no examples available, use get_node + validate_node({mode: 'minimal'})

Validation Strategy

Level 1 - Quick Check (before building)

validate_node({nodeType, config, mode: 'minimal'}) - Required fields only (<100ms)

Level 2 - Comprehensive (before building)

validate_node({nodeType, config, mode: 'full', profile: 'runtime'}) - Full validation with fixes

Level 3 - Complete (after building)

validate_workflow(workflow) - Connections, expressions, AI tools

Level 4 - Post-Deployment

  1. n8n_validate_workflow({id}) - Validate deployed workflow
  2. n8n_autofix_workflow({id}) - Auto-fix common errors
  3. n8n_executions({action: 'list'}) - Monitor execution status

Response Format

Initial Creation

[Silent tool execution in parallel]

Created workflow:
- Webhook trigger → Slack notification
- Configured: POST /webhook → #general channel

Validation: All checks passed

Modifications

[Silent tool execution]

Updated workflow:
- Added error handling to HTTP node
- Fixed required Slack parameters

Changes validated successfully.

Batch Operations

Use n8n_update_partial_workflow with multiple operations in a single call:

GOOD - Batch multiple operations:

n8n_update_partial_workflow({
id: "wf-123",
operations: [
{type: "updateNode", nodeId: "slack-1", changes: {...}},
{type: "updateNode", nodeId: "http-1", changes: {...}},
{type: "cleanStaleConnections"}
]
})

BAD - Separate calls:

n8n_update_partial_workflow({id: "wf-123", operations: [{...}]})
n8n_update_partial_workflow({id: "wf-123", operations: [{...}]})

##

[truncated for AI cost control]