Happy slice of mcp pizzaMCP.pizza

n8n-mcp-server

MCP.Pizza Chef: illuminaresolutions

Thirty-three tools cover the n8n automation service you already run: workflows, past runs, tags, users, variables, saved logins and a security audit. Two gaps between the instructions and the code are worth knowing first. The setup snippet tells you to store your address and key as hidden settings, but nothing in the program ever reads them, so the only way in is typing both into the chat. And despite the feature list there is no tool that runs a workflow on demand; you can only switch one on or off.

Unmaintained · No commits in 19 months.
Data
Other

Use This MCP server To

See every automation I have and which ones are running Turn a specific automation on or off Look into why a recent run failed Create a new automation and give it a name Tag and group my automations so I can find them Run a security check across my automation setup

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

  1. Log into your n8n instance
  2. Click your user icon in the bottom left
  3. Go to Settings
  4. Select API
  5. Click "Create API Key"
  6. 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

  1. Clone the repository:

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

  2. Install dependencies and build:

    npm install
npm run build

  3. 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.

n8n-mcp-server FAQ

Is it still maintained?
It has been quiet for a long time — no code changes since February 2025. n8n itself has moved on considerably in that period, so expect some rough edges, and the project does not point to a successor.
Does the setup shown in the instructions actually work?
Not the part about hidden settings. The code never reads an environment setting anywhere, so the address and key you are told to put there are simply ignored. In practice you connect by giving your n8n address and key to the tool inside the conversation, which means that key ends up stored in your chat history.
Do I need an access key?
Yes, but you create it yourself. Inside your own n8n, open Settings, find the section for programme access, and generate a key there. There is no separate sign-up, and the key carries whatever permissions your n8n account already has.
Can it actually run a workflow for me?
No, despite what the feature list says. There is no run tool anywhere in the code. You can switch a workflow on or off and read the history of runs that already happened, but starting one on demand is still n8n's job.
Can it delete things?
Yes, freely. There are seven separate delete tools covering workflows, projects, users, variables, saved logins, past runs and tags, and not one of them pauses to ask you to confirm.
Which apps does it work in?
Claude Desktop and VS Code with the Cline extension are both documented, and anything else that starts a local program from a settings snippet will work. The marketplace listing the instructions mention is still described there as coming soon.
Will everything work on a free n8n?
No. Projects, variables and the fuller user management need an n8n Enterprise licence. Without one, those tools come back with a licence error while the workflow and run tools keep working.
Can I use this to find out why an automation stopped working?
Yes. Ask for the recent runs and then pull the detail on a failed one, and you get the same record you would find by clicking through n8n yourself.
Anything else I should be careful about?
One tool creates saved logins for other services inside n8n, which means those passwords and access codes travel through the conversation on their way there.