
n8n MCP
β 22,100from czlonkowski
n8n MCP server that gives AI assistants access to n8n node documentation, properties, operations, and workflow automation context.
n8n-MCP
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 2,063 workflow automation nodes (816 core + 1,247 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:
-
2,063 n8n nodes - 816 core nodes + 1,247 community nodes (1,113 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
sourcefilter
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!
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
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
-
Start: Call
tools_documentation()for best practices -
Template Discovery Phase (FIRST - parallel when searching multiple)
search_templates({searchMode: 'by_metadata', complexity: 'simple'})- Smart filteringsearch_templates({searchMode: 'by_task', task: 'webhook_processing'})- Curated by tasksearch_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: 15for quick wins - By service:
requiredService: "openai"for compatibility
- 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 nodessearch_nodes({query: 'trigger'})- Browse triggerssearch_nodes({query: 'AI agent langchain'})- AI-capable nodes
- 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 propertiesget_node({nodeType, mode: 'docs'})- Human-readable markdown documentation- Show workflow architecture to user for approval before proceeding
- Validation Phase (parallel for multiple nodes)
validate_node({nodeType, config, mode: 'minimal'})- Quick required fields checkvalidate_node({nodeType, config, mode: 'full', profile: 'runtime'})- Full validation with fixes- Fix ALL errors before proceeding
- 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)
- Workflow Validation (before deployment)
validate_workflow(workflow)- Complete validationvalidate_workflow_connections(workflow)- Structure checkvalidate_workflow_expressions(workflow)- Expression validation- Fix ALL issues before deployment
- Deployment (if n8n API configured)
n8n_create_workflow(workflow)- Deployn8n_validate_workflow({id})- Post-deployment checkn8n_update_partial_workflow({id, operations: [...]})- Batch updatesn8n_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 ( Save these instructions in your Claude Project for optimal n8n workflow assistance with intelligent template discovery.
Available MCP Tools
Core Tools (7 tools)
-
tools_documentation- Get documentation for any MCP tool (START HERE!) -
search_nodes- Full-text search across all nodes. Usesource: 'community'|'verified'for community nodes,includeExamples: truefor configs -
get_node- Unified node information tool with multiple modes: -
Info mode (default):
detail: 'minimal'|'standard'|'full',includeExamples: true -
Docs mode:
mode: 'docs'- Human-readable markdown documentation -
Property search:
mode: 'search_properties',propertyQuery: 'auth' -
Versions:
mode: 'versions'|'compare'|'breaking'|'migrations' -
validate_node- Unified node validation: -
mode: 'minimal'- Quick required fields check (<100ms) -
mode: 'full'- Comprehensive validation with profiles (minimal, runtime, ai-friendly, strict) -
validate_workflow- Complete workflow validation including AI Agent validation -
search_templates- Unified template search: -
searchMode: 'keyword'(default) - Text search withqueryparameter -
searchMode: 'by_nodes'- Find templates using specificnodeTypes -
searchMode: 'by_task'- Curated templates for commontasktypes -
searchMode: 'by_metadata'- Filter bycomplexity,requiredService,targetAudience -
get_template- Get complete workflow JSON (modes: nodes_only, structure, full)
n8n Management Tools (16 tools - Requires API Configuration)
These tools require N8N_API_URL and N8N_API_KEY in your configuration.
Workflow Management
-
n8n_create_workflow- Create new workflows with nodes and connections -
n8n_get_workflow- Unified workflow retrieval (modes: full, details, structure, minimal) -
n8n_update_full_workflow- Update entire workflow (complete replacement) -
n8n_update_partial_workflow- Update workflow using diff operations -
n8n_delete_workflow- Delete workflows permanently -
n8n_list_workflows- List workflows with filtering and pagination -
n8n_validate_workflow- Validate workflows in n8n by ID -
n8n_autofix_workflow- Automatically fix common workflow errors -
n8n_workflow_versions- Manage version history and rollback -
n8n_deploy_template- Deploy templates from n8n.io directly to your instance with auto-fix
Execution Management
-
n8n_test_workflow- Test/trigger workflow execution (webhook, form, chat) -
n8n_executions- Unified execution management (list, get, delete)
Data Table Management
n8n_manage_datatable- Manage n8n data tables and rows (list, get, create, update, delete)
Credential Management
n8n_manage_credentials- Manage n8n credentials (list, get, create, update, delete, getSchema)
Security & Audit
n8n_audit_instance- Security audit combining n8n's built-in audit API with deep workflow scanning
System Tools
n8n_health_check- Check n8n API connectivity and features
Read-Only Deployment
For governance-sensitive environments, use both env vars together. Fully disable tools that are write/destructive or handle sensitive data (n8n_manage_credentials and n8n_manage_datatable also offer read operations, but are removed entirely here because even reads expose sensitive material):
DISABLED_TOOLS=n8n_create_workflow,n8n_update_full_workflow,n8n_update_partial_workflow,n8n_delete_workflow,n8n_autofix_workflow,n8n_deploy_template,n8n_test_workflow,n8n_manage_credentials,n8n_manage_datatable
For tools that bundle read and write operations under one name, block only the destructive operations while keeping list and get:
DISABLED_TOOL_OPERATIONS=n8n_workflow_versions:delete,rollback,prune;n8n_executions:delete
Combine with a read-only n8n API key (Settings β API in your n8n instance) for defence in depth. See Read-Only Deployment Recipe for the full setup guide.
Documentation
-
Self-Hosting Guide - npx, Docker, Railway, and local installation
-
Security & Hardening - Trust model, hardening options, workflow restrictions
-
n8n Deployment Guide - Production deployment with n8n
-
Database Configuration - SQLite adapters and memory optimization
-
Privacy & Telemetry - What we collect and how to opt out
-
Workflow Diff Operations - Token-efficient workflow updates
-
HTTP Deployment - Remote server setup
-
Change Log - Complete version history
License
MIT License - see LICENSE for details.
Contributing
See CONTRIBUTING.md for development setup, testing, and contribution guidelines.
Acknowledgments
See Acknowledgments for credits and template attribution.
Built with care for the n8n community
Quick Start
The fastest way to try n8n-MCP - no installation, no configuration:
-
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.
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.No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.