mcp-n8n-builder
@spences10
🪄 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.
概览
What is mcp-n8n-builder?
A Model Context Protocol (MCP) server for programmatic creation and management of n8n workflows. It provides tools and resources for interacting with n8n's REST API, allowing AI assistants to build, modify, and manage workflows without direct user intervention.
How to use mcp-n8n-builder?
Configure the server in your MCP client by providing the N8N_HOST (default http://localhost:5678/api/v1) and N8N_API_KEY environment variables, and optionally OUTPUT_VERBOSITY (default concise). Use tools like list_workflows, create_workflow, get_workflow, update_workflow, delete_workflow, activate_workflow, deactivate_workflow, list_available_nodes, list_executions, and get_execution.
Key features of mcp-n8n-builder
- Create, read, update, delete, activate, and deactivate workflows
- List and retrieve workflow execution details
- Comprehensive validation with Zod for input and output data
- Validates node types against n8n's available nodes before creation
- Provides suggestions for similar node types when invalid nodes detected
- Search and filter workflows by name, tags, or active status
Use cases of mcp-n8n-builder
- Automating n8n workflow creation and configuration via AI assistants
- Managing multiple workflows programmatically without manual UI interaction
- Debugging workflow executions by retrieving detailed execution data
- Validating workflow structures against available n8n node types before deployment
- Listing and filtering workflows to monitor active and inactive states
FAQ from mcp-n8n-builder
How do I configure the server?
Set N8N_HOST (URL of n8n API, default http://localhost:5678/api/v1) and N8N_API_KEY in environment variables. Optionally set OUTPUT_VERBOSITY to concise (default) or full.
Why is this tool called a "token monster"?
N8N workflows are complex JSON structures with nested nodes, connections, parameters, and settings. A single workflow can consume thousands of tokens, and the JSON structure cannot be meaningfully reduced without losing essential information.
How can I reduce token usage?
Use OUTPUT_VERBOSITY=concise for summaries instead of full JSON, list workflows first, work with simple workflows, break complex workflows into smaller pieces, and consider token cost before retrieving or editing large workflows.
What MCP tools are available?
The server provides tools for node management (list_available_nodes), workflow management (create_workflow, get_workflow, update_workflow, delete_workflow, activate_workflow, deactivate_workflow), and execution management (list_executions, get_execution).
What resources does the server expose?
The server exposes n8n://workflows (list of all workflows), n8n://workflows/{id} (details of a specific workflow), and n8n://executions/{id} (details of a workflow execution).
