📌Overview

Purpose: The n8n MCP server provides secure and standardized access to n8n workflows, executions, and credentials for Large Language Models (LLMs) via the Model Context Protocol.

Overview: The n8n MCP server enables seamless interaction between LLMs and n8n instances, allowing for efficient management and execution of workflows while ensuring data integrity and security.

Key Features:

Workflow Management: List, manage, and view details of workflows directly through the MCP server, facilitating easier workflow oversight.
Execution Capabilities: Execute workflows and handle tasks related to credential management, allowing for dynamic integration with LLMs.
Security Audits and Tag Management: Generate security audits and manage workflow tags to maintain organizational security and optimize workflow functionality.
Enterprise Integration: For enterprise users, advanced features like project and variable management are available to support complex organizational needs.

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)

npm install -g @illuminaresolutions/n8n-mcp-server

Option 2: Install from Source

Clone the repository:

git clone https://github.com/illuminaresolutions/n8n-mcp-server.git
cd n8n-mcp-server

Install dependencies and build:
```
npm install
npm run build
```

Start 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 file:

~/Library/Application Support/Claude/claude_desktop_config.json

Add 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

GitHub Issues: https://github.com/illuminaresolutions/n8n-mcp-server/issues
n8n Documentation: https://docs.n8n.io

License

MIT License