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`.
MCP N8n Builder
@spences10
基本情報
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.
MCP N8n Builder の設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"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"
}
}
}
}MCP N8n Builder のツール
10Lists 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
概要
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
よくある質問
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).
「開発者ツール」の他のコンテンツ
Capgo MCP
Cap-goConsole, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app
Perfex CRM
themesicTurn Perfex CRM into an AI-ready workspace. This MCP server exposes your full REST API to Claude, ChatGPT and any AI agent, so leads, invoices and tasks are one prompt away.
1
Apiosk
obcraftAI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·
Moxie Docs
Jackalope-DevAutomated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
1
Mcp-Warden
ermolukLocal-first credential broker for MCP. AI coding agents (Claude Code, Cursor, Codex…) call APIs, SSH and databases through scoped presets; secrets stay in your OS keychain and never enter the agent's context.
4
コメント