n8n Workflow Builder MCP
MCP server that builds n8n workflows as local JSON files: nodes, links, validation and version matching, no running n8n needed.
- 52 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The server writes workflow JSON files into the workspace.
- The optional `N8N_API_KEY` grants access to your n8n instance.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/n8n-workflow-builder-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The server writes workflow JSON files into the workspace.
- The optional `N8N_API_KEY` grants access to your n8n instance.
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent tools for assembling n8n workflows: `create_workflow`, `add_node`, `edit_node`, `add_connection`, `validate_workflow` and more. The result is saved as a JSON file that you import into n8n or commit to git. A running n8n instance is not required. The bundled node catalog covers n8n versions 1.86.0 to 2.6.2 and picks the closest suitable `typeVersion`. For AI chains there are `add_ai_connections`, `connect_main_chain` and `compose_ai_workflow`. Change plans can be reviewed with `plan_workflow` and `review_workflow_plan` before they are applied to the file.
Who it is for. Automation builders and developers on n8n who generate workflows in an agent and import them by hand or keep them in git.
Good fit when
- You need a workflow skeleton with a webhook, a model and agent memory, and `compose_ai_workflow` builds it in one call.
- You self-host an older n8n, and `N8N_VERSION` tells the server which node `typeVersion` values are supported.
- Workflows must live in a repository as JSON and pass `validate_workflow` before import.
- Edits first have to appear as a plan, and `review_workflow_plan` returns errors and warnings without writing the file.
- The agent fills in missing node parameters through `list_missing_parameters` and `fix_node_params`.
Not a fit when
- The agent has to run and debug workflows in a live n8n: use the built-in n8n MCP server.
- You need a large node documentation library and deployment through the API: the README points to `czlonkowski/n8n-mcp`.
- You need nodes added after version 2.6.2: they are not in the catalog yet.
Example request
Create a workflow lead-intake: a webhook takes a request, an AI Agent node with memory scores it and the result goes to Telegram. Check it with `validate_workflow`.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
N8N_API_URL- Address of your n8n, used to detect the version automatically.
N8N_API_KEYsecret- n8n API key, used only to detect the version.
N8N_VERSION- n8n version set by hand, for example 1.123.2, when no API key is given.
Limitations
The server only writes JSON files; running a workflow (`execute`) is not implemented. The node catalog is limited to n8n versions 1.86.0 to 2.6.2. The `N8N_API_KEY` key is optional and only detects the version of your n8n; without it set `N8N_VERSION`. Node.js 18 or newer is required. `validate_workflow` is strict: warnings become errors and nodes not connected to the main chain count as a failure.
How to disable. Run `claude mcp remove n8n-workflow-builder` or delete the block from `.vscode/mcp.json` or `.cursor/mcp.json`. The generated workflow JSON files stay in the workspace.
FAQ
Do I need a running n8n?
No. The server writes JSON locally and takes node versions from its catalog. You may supply an API URL and key to detect the version automatically.
How do I set the n8n version without the API?
With the `N8N_VERSION` environment variable, for example `N8N_VERSION=1.123.2`. No API key is needed then.
Which tools exist for AI chains?
`add_ai_connections` wires a model, tools and memory to an agent, `connect_main_chain` builds the main path, and `compose_ai_workflow` composes the full chain in one call.
How do I connect it in Cursor or VS Code?
Add the server to `.cursor/mcp.json` or `.vscode/mcp.json` with the command `npx` and arguments `-y n8n-workflow-builder-mcp`, then restart the editor.
Are there rules for Cursor?
Yes, the file `rules/n8n-mcp-server-rules.mdc` in the repository.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for n8n: an assistant creates, runs and deletes workflows through the API, checks executions and tags and requests a security audit
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
An MCP server for n8n: the agent manages workflows and their executions through the n8n API in natural language, creating, updating, activating and running them
Skills and hooks for building n8n workflows through the n8n-mcp server: expressions, nodes, validation, AI agents, self-hosting
n8n workflows for a Kommo CRM integration
Kommo MCP Server - n8n Workflows
A set of exported n8n workflows for Kommo CRM: a main orchestrator, individual webhooks per operation, and an example consumer agent
A plugin from the n8n team: 13 skills and a bundled MCP connection teach Claude Code and Codex to build, edit and validate n8n workflows
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| n8n Workflow Builder MCP (this card) | no | not required | 52 | |
| n8n-MCP | no | key is optional | 23,252 | carries a large documentation library and API deployment; this server writes version-matched JSON offline |
| n8n MCP Server | no | API key | 1,630 | manages a live n8n instance; this server assembles files with no connection |
README in short
The server builds n8n workflows offline as JSON, matching nodes against a version-aware catalog. It adds planning, validation and AI-chain tools.