SkillTide Submit
Official description3 sourcesMCP servers3d ago
czlonkowski/n8n-mcp

czlonkowski/n8n-mcp

Build n8n workflows with AI assistants
View on GitHub ↗Direct link · no redirect page
Source
collected from the abordage/awesome-mcp list · type: MCP server
Harvest history
first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
Score
score 303 · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-14;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

n8n-MCP

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

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 3,135 workflow automation nodes (840 core + 2,295 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:
- **3,135 n8n nodes** - 840 core nodes + 2,295 community nodes (1,878 verified)
- **Node properties** - 99% coverage with detailed schemas
- **Node operations** - 66.5% coverage of available actions
- **Documentation** - 86% coverage from official n8n docs (including AI nodes)
- **AI tools** - 267 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**
> 💼 **Need it built for you?** Work with AiAdvisors — n8n automation audits, builds, and operations, run by the author of n8n-mcp and n8n-skills.
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
Cloudflare Access Authentication
If your n8n instance sits behind Cloudflare Access (Zero Trust), provide your service token so n8n-MCP can authenticate:
- N8N_CF_CLIENT_ID - Cloudflare Access Client ID
- N8N_CF_CLIENT_SECRET - Cloudflare Access Client Secret
When set, these are sent as CF-Access-Client-Id / CF-Access-Client-Secret headers on n8n API requests, version/health probes, and webhook executions. The token is confined to the N8N_API_URL origin — webhook calls to a different host (e.g. a split WEBHOOK_URL origin) do not receive it, to avoid leaking the token.
Source
awesome · https://github.com/czlonkowski/n8n-mcp
Browse by field
MCP servers
added
yesterday

More in MCP servers

All 5,525 in MCP servers →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index