n8n

This MCP server provides a bridge between AI assistants and an n8n workflow automation instance. It exposes tools that let you list workflows, inspect a workflow, create new workflows, and trigger n8n webhooks to run workflows. The webhook tool enables invoking workflow executions via n8n's webhook endpoints with optional authentication. Other tools let you fetch details about workflows to help the AI decide which actions to take next, and to create or modify workflows when needed. To integrate with an AI assistant, point the assistant’s MCP configuration at the built server (build/index.js) and supply the required N8N_API_URL and N8N_API_KEY as environment variables. You can also configure webhook credentials if you plan to use webhook-triggered workflows.

Prerequisites:

• Node.js 20 or later
• An accessible n8n instance with API access enabled

Install from npm (recommended for quick start):

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

After installation, build the project if you cloned the repo locally:

git clone https://github.com/leonardsellem/n8n-mcp-server.git
cd n8n-mcp-server
npm install
npm run build

Optionally install globally from the built source:

npm install -g .

Docker installation:

docker pull leonardsellem/n8n-mcp-server

Run with your n8n settings:

docker run -e N8N_API_URL=http://your-n8n:5678/api/v1 \
  -e N8N_API_KEY=your_n8n_api_key \
  -e N8N_WEBHOOK_USERNAME=username \
  -e N8N_WEBHOOK_PASSWORD=password \
  leonardsellem/n8n-mcp-server

Environment variables:

• N8N_API_URL: Full URL to the n8n API including /api/v1
• N8N_API_KEY: API key for authenticating with n8n
• N8N_WEBHOOK_USERNAME/N8N_WEBHOOK_PASSWORD: Optional if you plan to use webhook-triggered workflows
• DEBUG: Enable verbose logging (true/false)

Tips:

• Ensure the path in mcp_config points to the built index.js file if you’re running from a local clone. Absolute paths are recommended.
• If you don’t plan to use webhooks, you can omit webhook-related env vars, but keep N8N_API_URL and N8N_API_KEY configured.
• When updating, rebuild and restart the MCP server to pick up changes.