n8n

A comprehensive MCP (Model Context Protocol) server for N8N workflow automation, providing tools for managing workflows, executions, credentials, variables, and more through a standardized interface.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio kingler-n8n-mcp-server node /path/to/n8n-mcp-server/start.js \
  --env PORT="3000" \
  --env LOG_LEVEL="info" \
  --env N8N_API_KEY="your-api-key-here" \
  --env N8N_API_URL="http://localhost:5678/api/v1"

How to use

This MCP server exposes a comprehensive set of tools to interact with an n8n instance via the Model Context Protocol. It provides complete coverage of n8n APIs, including workflows, executions, credentials, tags, users, variables, and file uploads, along with health checks and robust error handling. The server supports blocking and batch operations, input validation, retry logic, and rate limiting to ensure reliable interactions even in unstable network conditions. Use the available tools to list, create, update, and manage workflows, trigger and monitor executions, manage credentials and variables, and perform administrative tasks like tagging and user lookups. To begin, configure your client (Claude Desktop or other MCP clients) with the server's details and the required environment variables (N8N_API_URL, N8N_API_KEY). Once connected, you can list workflows, trigger executions, manage credentials, and check health status through the provided toolset, all with consistent error reporting and typed inputs.

How to install

Prerequisites:

Node.js 18.0.0 or higher
npm (comes with Node.js)
Access to an running n8n instance with API access

Installation steps:

Clone the repository

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

Install dependencies

npm install

Configure environment

cp .env.example .env

Edit .env with your n8n configuration and any required settings (see environment variables in README).

Build the project (if applicable)

npm run build

Run the server

npm start

Optional: Run in development mode

npm run dev

Prerequisites summary ensured: Node.js 18+ installed, n8n instance accessible, and API key available.

Additional notes

Tips and common issues:

Ensure N8N_API_URL and N8N_API_KEY are correct; invalid credentials will yield authentication errors with clear error codes.
If you encounter connection timeouts, adjust API_TIMEOUT and API_RETRY_* settings in the client configuration.
Use the provided CLI and tool names (e.g., list_workflows, trigger_execution) to explore capabilities and validate permissions.
Enable verbose logging in development to capture detailed traces for troubleshooting.
The server uses Zod for input validation, so you’ll receive structured validation errors when inputs don’t match the expected schema.
For Claude Desktop or other MCP clients, ensure the path to start.js and environment variables align with your deployment layout.
If you add custom n8n instances, remember to rotate API keys regularly and restrict permissions as needed.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.