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.