MCP 服务器

MCP- N8N

N8N MCP

Tools

init-n8n

Initialize connection to n8n instance. Use this tool whenever an n8n URL and API key are shared to establish the connection. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

list-workflows

List all workflows from n8n. Use after init-n8n to see available workflows. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

get-workflow

Retrieve a workflow by ID. Use after list-workflows to get detailed information about a specific workflow. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

create-workflow

Create a new workflow in n8n. Use to set up a new workflow with optional nodes and connections. IMPORTANT: 1) Arguments must be provided as compact, single-line JSON without whitespace or newlines. 2) Must provide full workflow structure including nodes and connections arrays, even if empty. The 'active' property should not be included as it is read-only.

update-workflow

Update an existing workflow in n8n. Use after get-workflow to modify a workflow's properties, nodes, or connections. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

delete-workflow

Delete a workflow by ID. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

activate-workflow

Activate a workflow by ID. This will enable the workflow to run. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

deactivate-workflow

Deactivate a workflow by ID. This will prevent the workflow from running. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

list-projects

List all projects from n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

create-project

Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

delete-project

Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

update-project

Update a project's name. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

list-users

Retrieve all users from your instance. Only available for the instance owner.

create-users

Create one or more users in your instance.

get-user

Get user by ID or email address.

delete-user

Delete a user from your instance.

list-variables

List all variables from n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after init-n8n to see available variables. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

create-variable

Create a new variable in n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Variables can be used across workflows to store and share data. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

delete-variable

Delete a variable by ID. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after list-variables to get the ID of the variable to delete. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

create-credential

Create a credential that can be used by nodes of the specified type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). Use get-credential-schema first to see what fields are required for the credential type you want to create.

delete-credential

Delete a credential by ID. You must be the owner of the credentials.

get-credential-schema

Show credential data schema for a specific credential type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). This will show you what fields are required for creating credentials of this type.

list-executions

Retrieve all executions from your instance with optional filtering.

get-execution

Retrieve a specific execution by ID.

delete-execution

Delete a specific execution by ID.

create-tag

Create a new tag in your instance.

list-tags

Retrieve all tags from your instance.

get-tag

Retrieve a specific tag by ID.

update-tag

Update a tag's name.

delete-tag

Delete a tag by ID.

get-workflow-tags

Get tags associated with a workflow.

update-workflow-tags

Update tags associated with a workflow.

generate-audit

Generate a security audit for your n8n instance.

README

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:

~/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

License

MIT License