The n8n MCP Server enables LLMs to securely interact with n8n instances via the Model Context Protocol (MCP), providing comprehensive workflow and resource management capabilities:
Initialize connections to n8n instances using URL and API key
Workflow Management: List, create, update, delete, activate, deactivate, and retrieve workflows
Execution Management: List, retrieve, and delete workflow executions
Credential Management: Create, delete, and retrieve credential schemas
Tag Management: Create, list, update, delete tags and manage workflow tags
User Management: List, create, retrieve, and delete users
Project Management: List, create, update, and delete projects (requires Enterprise license)
Variable Management: List, create, and delete variables (requires Enterprise license)
Security: Generate security audits for the n8n instance
Provides tools for managing n8n workflows, executions, credentials, tags, projects, users, and variables. Allows creating, retrieving, updating, and deleting workflows, executing workflows, managing workflow tags, and generating security audits for n8n instances.
Mentioned as a future platform where the n8n MCP server will be available through the Smithery.ai marketplace.
n8n MCP Server
An MCP server that provides access to n8n workflows, executions, credentials, and more through the Model Context Protocol. This allows Large Language Models (LLMs) to interact with n8n instances in a secure and standardized way.
Installation
Get your n8n API Key
Log into your n8n instance
Click your user icon in the bottom left
Go to Settings
Select API
Click "Create API Key"
Copy your API key (you won't be able to see it again)
Install the MCP Server
Option 1: Install from npm (Recommended)
Option 2: Install from Source
Clone the repository:
git clone https://github.com/illuminaresolutions/n8n-mcp-server.git cd n8n-mcp-serverInstall dependencies and build:
npm install npm run buildStart the server in the background:
nohup npm start > n8n-mcp.log 2>&1 &To stop the server:
pkill -f "node build/index.js"
Note: When installing from npm, the server will be available as n8n-mcp-server
in your PATH.
Configuration
Claude Desktop
Open your Claude Desktop configuration:
~/Library/Application Support/Claude/claude_desktop_config.jsonAdd the n8n configuration:
{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }
Cline (VS Code)
Install the server (follow Installation steps above)
Open VS Code
Open the Cline extension from the left sidebar
Click the 'MCP Servers' icon at the top of the pane
Scroll to bottom and click 'Configure MCP Servers'
Add to the opened settings file:
{ "mcpServers": { "n8n": { "command": "n8n-mcp-server", "env": { "N8N_HOST": "https://your-n8n-instance.com", "N8N_API_KEY": "your-api-key-here" } } } }Save the file
Ensure the MCP toggle is enabled (green) and the status indicator is green
Start using MCP commands in Cline
Sage
Coming soon! The n8n MCP server will be available through:
Smithery.ai marketplace
Import from Claude Desktop
For now, please use Claude Desktop or Cline.
Validation
After configuration:
Restart your LLM application
Ask: "List my n8n workflows"
You should see your workflows listed
If you get an error:
Check that your n8n instance is running
Verify your API key has correct permissions
Ensure N8N_HOST has no trailing slash
Features
Core Features
List and manage workflows
View workflow details
Execute workflows
Manage credentials
Handle tags and executions
Generate security audits
Manage workflow tags
Enterprise Features
These features require an n8n Enterprise license:
Project management
Variable management
Advanced user management
Troubleshooting
Common Issues
"Client not initialized"
Check N8N_HOST and N8N_API_KEY are set correctly
Ensure n8n instance is accessible
Verify API key permissions
"License required"
You're trying to use an Enterprise feature
Either upgrade to n8n Enterprise or use core features only
Connection Issues
Verify n8n instance is running
Check URL protocol (http/https)
Remove trailing slash from N8N_HOST
Security Best Practices
API Key Management
Use minimal permissions necessary
Rotate keys regularly
Never commit keys to version control
Instance Access
Use HTTPS for production
Enable n8n authentication
Keep n8n updated
Support
License
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Tools
An MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).
Related Resources
Related MCP Servers
- -securityAlicense-qualityA Model Context Protocol (MCP) compliant server that allows Large Language Models (LLMs) to search and retrieve content from microCMS APIs.Last updated -MIT License
- AsecurityAlicenseAqualityA Model Context Protocol (MCP) server for programmatically creating and managing n8n workflows.Last updated -120MIT License
- AsecurityAlicenseAquality🪄 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.Last updated -103273MIT License
- AsecurityAlicenseAqualityA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).Last updated -1242Apache 2.0