概要
What is n8n Workflow Builder MCP Server?
A Model Context Protocol (MCP) server that bridges AI assistants (such as Claude Desktop, ChatGPT, or any MCP-compatible client) with an n8n automation instance. It enables natural-language workflow management, creation, execution, and monitoring through the n8n API.
How to use n8n Workflow Builder MCP Server?
Install via NPX (npx @makafeli/n8n-workflow-builder) or use the hosted Smithery.ai version. Set environment variables N8N_HOST (your n8n URL) and N8N_API_KEY (from n8n Settings > API Keys). Configure the server in your MCP client (e.g., Claude Desktop, Cline) with the same command and env values.
Key features of n8n Workflow Builder MCP Server
- Complete CRUD operations for n8n workflows
- AI-first design built for assistant integration
- Zero configuration with NPX run
- Secure via n8n official API with authentication
- Modern TypeScript architecture with MCP SDK
- High performance with optimized response times
Use cases of n8n Workflow Builder MCP Server
- List and browse existing n8n workflows through conversation
- Create new workflows with complex node configurations
- Execute workflows on demand via natural language
- Manage workflow lifecycle (activate, deactivate, update, delete)
FAQ from n8n Workflow Builder MCP Server
What are the system requirements?
Node.js v18.0.0 or higher, a running n8n instance (self-hosted or cloud), and an n8n API key with appropriate permissions.
How do I get an n8n API key?
In your n8n instance, go to Settings → API Keys → Create API Key, then copy the generated key.
Is there a hosted version available?
Yes, the server is available as a hosted service on Smithery.ai with no local installation required.
Which MCP clients are supported?
The server works with any MCP-compatible client; explicit setup instructions are provided for Claude Desktop and Cline (VS Code extension).
How do I configure environment variables?
Set N8N_HOST to your n8n instance URL (e.g., http://localhost:5678) and N8N_API_KEY to your API key, then export them or include them in your MCP client’s config JSON.
