AI-powered n8n workflow management via Model Context Protocol (MCP). Create, manage, and monitor workflows through natural language with Claude AI.
AI-powered n8n workflow management via Model Context Protocol (MCP). Create, manage, and monitor workflows through natural language with Claude AI. Multi-instance support with comprehensive documentation. That is what the mcp n8n workflow builder mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 14 tools. What each one is for:
list_workflows — List all workflows with filteringget_workflow — Retrieve complete workflow detailscreate_workflow — Build new workflows from scratchupdate_workflow — Modify existing workflowsdelete_workflow — Remove workflowsactivate_workflow — Enable workflow executiondeactivate_workflow — Disable workflow executionexecute_workflow — Manually trigger workflow runslist_executions — View execution history with filtersget_execution — Detailed execution informationdelete_execution — Remove execution recordsretry_execution — Retry failed workflow runsConfiguration is passed through the environment: N8N_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @kernel.salacoste/n8n-workflow-builder, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP N8n Workflow Builder's toolset — list_workflows, get_workflow, create_workflow and 11 more — is a fair guide to whether it matches your workflow. It is maintained by salacoste; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP N8n Workflow Builder's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_workflows | List all workflows with filtering |
| get_workflow | Retrieve complete workflow details |
| create_workflow | Build new workflows from scratch |
| update_workflow | Modify existing workflows |
| delete_workflow | Remove workflows |
| activate_workflow | Enable workflow execution |
| deactivate_workflow | Disable workflow execution |
| execute_workflow | Manually trigger workflow runs |
| list_executions | View execution history with filters |
| get_execution | Detailed execution information |
| delete_execution | Remove execution records |
| retry_execution | Retry failed workflow runs |
| get_tag | Get specific tag information |
| create_tag | Create workflow organization tags |
{
"mcpServers": {
"n8n-workflow-builder": {
"command": "npx",
"args": ["-y", "@kernel.salacoste/n8n-workflow-builder"],
"env": {
"N8N_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| N8N_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.