A — Few risk signals Graded October 16, 2026Strong public adoption and transparency signals.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.
App connector · Developer tools
n8n-mcp
A MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you
Bottom line: Signal-based grade (6/7 points): very widely starred on GitHub, listed in several sources, public source code. This reflects adoption and transparency, not a code review.
- Popularity score
- 84/100
- Rank
- #6 of 500
- GitHub stars
- 23.1k
- Weekly downloads
- 48.2k
What it does
n8n-mcp is a Model Context Protocol connector that enables Claude Desktop, Claude Code, Windsurf, and Cursor to programmatically build and manage n8n workflows. It bridges AI coding assistants with n8n's no-code automation platform, allowing agents to create workflow definitions, configure nodes, and deploy automations.
Who it’s for
DevOps engineers, workflow automation builders, and technical teams using n8n who want AI-assisted workflow generation and management. Best suited for organizations already invested in the n8n ecosystem seeking to accelerate workflow development.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Install via npm and configure in Claude Desktop's mcpServers JSON:
npm install -g n8n-mcp
Then add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or Windows equivalent:
{
"mcpServers": {
"n8n-mcp": {
"command": "npx",
"args": ["n8n-mcp"]
}
}
}
Verify against the repo README (opens external site) for the latest configuration and required n8n API credentials.
Risks
- Credential scope: Requires n8n API tokens; ensure tokens are scoped minimally and never hardcoded in config files or prompts.
- Prompt injection: AI agents could be manipulated to generate malicious workflow nodes or exfiltrate data via crafted workflow definitions.
- Supply-chain dependency: Relies on maintainer's continued updates; single unmaintained MCP could leave deployments vulnerable.
- Data exfiltration: Agents with workflow-building access can create data pipelines that export sensitive information to external webhooks or APIs.
- Audit trail gaps: Workflow creation via MCP may bypass n8n's native access controls or leave incomplete audit logs of who initiated changes.
How to stay secure
Least-privilege permissions
- Create dedicated n8n API tokens for the MCP with minimal scopes (workflow creation only, no credentials/secrets management).
- Rotate API tokens every 30 days; revoke immediately if exposed.
- Use n8n's Team/Project-level permissions to restrict which workflows the MCP can create or modify.
- Never pass n8n credentials in prompts, environment variables, or config files—use secure credential storage (e.g., 1Password, HashiCorp Vault).
Network isolation
- Run n8n-mcp and n8n instances on the same private network; restrict external API access to whitelisted destinations only.
- Disable webhook outputs by default; require explicit allowlisting of external URLs before workflows can export data.
- Use egress filtering to prevent workflows from reaching unauthorized APIs, SaaS platforms, or cloud storage services.
Monitoring
- Enable n8n audit logging and send logs to a SIEM (Splunk, DataDog, etc.) to track all MCP-initiated workflow changes.
- Alert on suspicious patterns: workflows calling external webhooks, credential access attempts, or bulk data exports.
- Review workflow definitions created via MCP monthly; audit node configurations for hardcoded secrets or unexpected API destinations.
- Monitor MCP API token usage for anomalies (high request rates, unexpected scopes, errors).
Red flags to watch for
- Workflows with hardcoded URLs pointing to external webhook collectors or suspicious domains.
- Prompts or logs containing n8n credentials, API keys, or sensitive configuration snippets.
- Workflows accessing n8n's Credentials node or secrets endpoints when the token should only allow workflow creation.
- Unmaintained n8n-mcp repository (no commits >6 months) or unpatched CVEs in dependencies—fork and maintain internally.
Alternatives
- Zapier API connector (opens external site) — Similar automation platform with native API; more mature but less developer-friendly for MCP integration.
- Make (Integromat) API (opens external site) — Alternative no-code platform with REST API for programmatic workflow creation.
- n8n native CLI (opens external site) — Direct command-line workflow management without MCP overhead; better for local CI/CD pipelines.
- Custom n8n webhook triggers (opens external site) — Use n8n's native webhook node to let AI agents trigger workflows instead of building them.