
mcp-n8n-builder
🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.
Tools
list_available_nodes
Lists all available nodes in the n8n instance. Use this tool BEFORE creating or updating workflows to ensure you only use valid node types. This helps prevent errors caused by using node types that do not exist in the current n8n instance.
list_workflows
Lists all workflows from n8n with their basic information including ID, name, status, creation date, and tags. Use this tool to get an overview of available workflows before performing operations on specific workflows. Results can be filtered by active status, tags, or name.
create_workflow
Creates a new workflow in n8n with specified nodes and connections. Note that only workflows with automatic trigger nodes (schedule, webhook, etc.) can be activated - workflows with only manual triggers cannot be activated. Returns the created workflow with its assigned ID.
get_workflow
Retrieves complete details of a specific workflow by its ID, including all nodes, connections, settings, and metadata. Use this tool when you need to examine a workflow's structure before updating it or to understand how it works.
update_workflow
Updates an existing workflow with new configuration. Typically used after retrieving a workflow with get_workflow, modifying its structure, and then saving the changes. The entire workflow structure must be provided, not just the parts being changed.
delete_workflow
Permanently deletes a workflow by its ID. This action cannot be undone, so use with caution. Consider deactivating workflows instead if you might need them again later.
activate_workflow
Activates a workflow by its ID, enabling it to run automatically based on its trigger (schedule, webhook, etc.). Note that only workflows with automatic trigger nodes can be activated - workflows with only manual triggers cannot be activated.
deactivate_workflow
Deactivates a workflow by its ID, preventing it from running automatically. The workflow will still exist and can be manually executed or reactivated later. Use this instead of deleting workflows that you might need again.
list_executions
Lists workflow execution history with details on success/failure status, duration, and timestamps. Use this tool to monitor workflow performance, troubleshoot issues, or verify that workflows are running as expected. Results can be filtered by workflow ID, status, and limited to a specific number.
get_execution
Retrieves detailed information about a specific workflow execution, including execution time, status, and optionally the full data processed at each step. Particularly useful for debugging failed workflows or understanding data transformations between nodes.
README
mcp-n8n-builder
A Model Context Protocol (MCP) server for programmatic creation and management of n8n workflows. This server provides tools and resources for interacting with n8n's REST API, allowing AI assistants to build, modify, and manage workflows without direct user intervention.
<a href="https://glama.ai/mcp/servers/@spences10/mcp-n8n-builder"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@spences10/mcp-n8n-builder/badge" /> </a>
Features
- 🔄 Workflow Management: Create, read, update, delete, activate, and deactivate workflows
- 📊 Execution Management: List and retrieve workflow execution details
- ✅ Schema Validation: Comprehensive validation with Zod for both input and output data
- 🔍 Node Validation: Validates node types against n8n's available nodes before workflow creation to prevent errors
- 🤔 Smart Suggestions: Provides suggestions for similar node types when invalid nodes are detected
- 🛠️ Error Handling: Detailed error messages for troubleshooting
- 📝 Documentation: Extensive documentation for all tools and resources
- 🔍 Search & Filter: Filter workflows by name, tags, or active status
Configuration
This server requires configuration through your MCP client. Here are examples for different environments:
Cline Configuration
Add this to your Cline MCP settings:
{
"mcpServers": {
"n8n-workflow-builder": {
"command": "npx",
"args": ["-y", "mcp-n8n-builder"],
"env": {
"N8N_HOST": "http://localhost:5678/api/v1",
"N8N_API_KEY": "your-n8n-api-key",
"OUTPUT_VERBOSITY": "concise" // Options: 'concise' or 'full'
}
}
}
}
Claude Desktop with WSL Configuration
For WSL environments, add this to your Claude Desktop configuration:
{
"mcpServers": {
"n8n-workflow-builder": {
"command": "wsl.exe",
"args": [
"bash",
"-c",
"N8N_HOST=http://localhost:5678/api/v1 N8N_API_KEY=your-n8n-api-key OUTPUT_VERBOSITY=concise npx -y mcp-n8n-builder"
]
}
}
}
Environment Variables
The server can be configured using environment variables:
Variable | Description | Default |
---|---|---|
N8N_HOST |
URL of the n8n API | http://localhost:5678/api/v1 |
N8N_API_KEY |
API key for n8n authentication | "" |
SERVER_NAME |
Name of the MCP server | "n8n-workflow-builder" |
SERVER_VERSION |
Version of the MCP server | Package version |
LOG_LEVEL |
Logging level | "info" |
CACHE_ENABLED |
Enable caching | false |
CACHE_TTL |
Cache TTL in seconds | 300 |
OUTPUT_VERBOSITY |
Output verbosity level (concise or full ) |
"concise" |
MCP Tools
Node Management
list_available_nodes
: Lists all available nodes in the n8n instance. IMPORTANT: Use this tool BEFORE creating or updating workflows to ensure you only use valid node types. This helps prevent errors caused by using node types that don't exist in the current n8n instance.
Workflow Management
list_workflows
: Lists all workflows from n8n with their basic information including ID, name, status, creation date, and tags. Results can be filtered by active status, tags, or name.create_workflow
: Creates a new workflow in n8n with specified nodes and connections. Returns the created workflow with its assigned ID. Validates that all node types exist in the n8n instance.get_workflow
: Retrieves complete details of a specific workflow by its ID, including all nodes, connections, settings, and metadata.update_workflow
: Updates an existing workflow with new configuration. The entire workflow structure must be provided, not just the parts being changed. Validates that all node types exist in the n8n instance.delete_workflow
: Permanently deletes a workflow by its ID. This action cannot be undone.activate_workflow
: Activates a workflow by its ID, enabling it to run automatically based on its trigger.deactivate_workflow
: Deactivates a workflow by its ID, preventing it from running automatically.
Execution Management
list_executions
: Lists workflow execution history with details on success/failure status, duration, and timestamps. Results can be filtered by workflow ID, status, and limited to a specific number.get_execution
: Retrieves detailed information about a specific workflow execution, including execution time, status, and optionally the full data processed at each step.
MCP Resources
n8n://workflows
: List of all workflows in n8nn8n://workflows/{id}
: Details of a specific n8n workflown8n://executions/{id}
: Details of a specific n8n workflow execution
Development
Setup
- Clone the repository
- Install dependencies:
npm install
- Build the project:
npm run build
- Run in development mode:
npm run dev
Publishing
The project uses changesets for version management. To publish:
- Create a changeset:
npm changeset
- Version the package:
npm changeset version
- Publish to npm:
npm release
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
MIT License - see the LICENSE file for details.
Acknowledgments
- Built on the Model Context Protocol
- Powered by n8n
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.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.