n8n Workflow Builder MCP Server
A server for programmatically creating and managing n8n workflows with a REST API interface, supporting workflow creation, validation, and export.
makafeli
Tools
delete_workflow
Delete a workflow by ID
activate_workflow
Activate a workflow by ID
deactivate_workflow
Deactivate a workflow by ID
list_workflows
List all workflows from n8n
create_workflow
Create a new workflow in n8n
get_workflow
Get a workflow by ID
update_workflow
Update an existing workflow
list_executions
List all executions from n8n with optional filters
get_execution
Get details of a specific execution by ID
delete_execution
Delete an execution by ID
README
n8n Workflow Builder MCP Server
This project provides an MCP server for managing n8n workflows. It offers functionality to list, create, update, delete, activate, and deactivate workflows through a set of defined tools.
Important:
This version exclusively supports npm for package management and running the server. (npx support will be reintroduced in a future update.)
Requirements
- Node.js (v14+ recommended)
- npm
Extensive Installation Guide
1. Clone the Repository
Clone the repository from your preferred source. For example:
git clone https://github.com/makafeli/n8n-workflow-builder.git
Then, navigate to the project directory:
cd /root/n8n-workflow-builder
2. Install Dependencies
Install the necessary dependencies using npm:
npm install
This command will download and install all required packages as defined in the package.json
file.
3. Build and Test
For testing and getting the server online, use the following commands:
-
Build the project:
This compiles the TypeScript files and produces the executable JavaScript in thebuild
directory.npm run build
-
Start the MCP Server:
Launch the server using:npm start
The server will start and connect via stdio. You can check the console to see messages confirming that the server has started correctly.
4. Deployment
For testing purposes and to get the server online, use the build and start commands mentioned above. This basic workflow (install, build, start) is currently the recommended method.
5. Additional Configuration
Server configuration is managed via the cline_mcp_settings.json
file. Ensure that the following environment variables are correctly set:
N8N_HOST
: Your n8n API host URL.N8N_API_KEY
: Your n8n API key.
Example configuration in cline_mcp_settings.json
:
{
"n8n-workflow-builder": {
"command": "node",
"args": ["/root/n8n-workflow-builder/build/index.js"],
"env": {
"N8N_HOST": "https://n8n.io/api/v1/",
"N8N_API_KEY": "YOUR_N8N_API_KEY_HERE"
},
"disabled": false,
"alwaysAllow": [
"create_workflow",
"create_workflow_and_activate",
"update_workflow",
"activate_workflow",
"deactivate_workflow",
"get_workflow",
"delete_workflow"
],
"autoApprove": []
}
}
Available Features
MCP Tools
The following tools are defined in the server and can be accessed through your MCP client:
Workflow Management
- list_workflows: Lists all workflows from n8n.
- create_workflow: Creates a new workflow in n8n.
- get_workflow: Retrieves a workflow by its ID.
- update_workflow: Updates an existing workflow.
- delete_workflow: Deletes a workflow by its ID.
- activate_workflow: Activates a workflow by its ID.
- deactivate_workflow: Deactivates a workflow by its ID.
Execution Management
- list_executions: Lists all workflow executions with optional filters.
- get_execution: Retrieves details of a specific execution by its ID.
- delete_execution: Deletes an execution by its ID.
MCP Resources
The server also provides the following resources for more efficient context access:
Static Resources
- /workflows: List of all available workflows in the n8n instance
- /execution-stats: Summary statistics about workflow executions
Dynamic Resource Templates
- /workflows/{id}: Detailed information about a specific workflow
- /executions/{id}: Detailed information about a specific execution
Troubleshooting
- Ensure you are using npm (this version does not support npx).
- If you encounter any issues, try cleaning the build directory and rebuilding:
npm run clean && npm run build
- Verify that your environment variables in
cline_mcp_settings.json
are correct.
Future Enhancements
- Reintroduction of npx support.
- Additional tools and workflow features.
- Further enhancements to deployment and scaling.
License
This project is licensed under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
MCP Package Docs Server
Facilitates LLMs to efficiently access and fetch structured documentation for packages in Go, Python, and NPM, enhancing software development with multi-language support and performance optimization.
Claude Code MCP
An implementation of Claude Code as a Model Context Protocol server that enables using Claude's software engineering capabilities (code generation, editing, reviewing, and file operations) through the standardized MCP interface.
@kazuph/mcp-taskmanager
Model Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.
Linear MCP Server
Enables interaction with Linear's API for managing issues, teams, and projects programmatically through the Model Context Protocol.
mermaid-mcp-server
A Model Context Protocol (MCP) server that converts Mermaid diagrams to PNG images.
Jira-Context-MCP
MCP server to provide Jira Tickets information to AI coding agents like Cursor

Linear MCP Server
A Model Context Protocol server that integrates with Linear's issue tracking system, allowing LLMs to create, update, search, and comment on Linear issues through natural language interactions.

Sequential Thinking MCP Server
This server facilitates structured problem-solving by breaking down complex issues into sequential steps, supporting revisions, and enabling multiple solution paths through full MCP integration.