n8n MCP Server
An MCP server for n8n: the agent manages workflows and their executions through the n8n API in natural language, creating, updating, activating and running them
- 1,630 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Writes to an external automation system: creates, changes, activates, deletes and runs workflows
- Takes on the n8n API key's permissions and can affect production scenarios
Install
- Works in
Manual install
npm install -g @leonardsellem/n8n-mcp-serverGlobal install from npm. After this the server is available as the n8n-mcp-server command.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Writes to an external automation system: creates, changes, activates, deletes and runs workflows
- Takes on the n8n API key's permissions and can affect production scenarios
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to your n8n instance through its API and provides a set of tools for working with workflows and executions. Through them the agent lists workflows, reads and creates them, updates, activates and deactivates, deletes, and also runs workflows and inspects executions: list, details, re-run, delete of an execution record. The server runs over the stdio transport as a local process or in Docker and is configured through environment variables: the n8n API URL, the API key and, for webhook use, a username and password. The package is published on npm, installs globally or builds from the TypeScript source. It is a control bridge: the agent gives natural-language commands and the server turns them into n8n API calls.
Who it is for. For developers and automation engineers who run their own n8n and want to manage workflows through an agent.
Good fit when
- You need to manage n8n workflows from an agent: list, create, update, activate
- You need to run workflows and inspect their executions with the agent
- You need to connect your own n8n to an agent through MCP and the n8n API
Not a fit when
- You do not have your own n8n instance with the API enabled
- You cannot let the agent change and run production workflows
Example request
List all my n8n workflows and activate the one called report mailingMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
N8N_API_URLrequired- Full URL of the n8n API, including /api/v1
N8N_API_KEYrequired, secret- API key for accessing n8n, created in the n8n settings
N8N_WEBHOOK_USERNAME- Username for webhook authentication, if webhooks are used
N8N_WEBHOOK_PASSWORDsecret- Password for webhook authentication
DEBUG- Enable debug logging, true or false
Limitations
You need your own n8n instance with the API enabled and an API key. The server takes on that key's permissions, so the agent can change, activate and run workflows, including production ones: issue a key with the right scope and keep it secret. The latest release is version 0.1.8 with no updates for a long time, and the MCP SDK version it uses is old, which may affect compatibility with newer clients. Webhook use needs a separate username and password.
How to disable. Remove the server entry from the MCP client configuration. For a global install remove the package: npm uninstall -g @leonardsellem/n8n-mcp-server. To revoke access disable the API key in n8n settings.
FAQ
How do I issue an n8n API key?
In the n8n UI open Settings, then API, then API Keys, create a key with the needed scope and put it in the N8N_API_KEY variable.
Can it run in Docker?
Yes. There is an image that runs with the same environment variables: the API URL, the key and, if needed, a username and password for webhooks.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
An MCP server for n8n: an assistant creates, runs and deletes workflows through the API, checks executions and tags and requests a security audit
n8n workflows for a Kommo CRM integration
Kommo MCP Server - n8n Workflows
A set of exported n8n workflows for Kommo CRM: a main orchestrator, individual webhooks per operation, and an example consumer agent
A plugin from the n8n team: 13 skills and a bundled MCP connection teach Claude Code and Codex to build, edit and validate n8n workflows
Skills and hooks for building n8n workflows through the n8n-mcp server: expressions, nodes, validation, AI agents, self-hosting
MCP server that builds n8n workflows as local JSON files: nodes, links, validation and version matching, no running n8n needed.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| n8n MCP Server (this card) | no | API key | 1,630 | |
| n8n Workflows: the Zie619 collection | no | 57,231 | 4,343 workflows with search and Docker | |
| Awesome n8n Templates | no | 26,386 | 280 templates in topic folders |
README in short
The README describes an MCP server that lets an agent manage n8n through its API in natural language. It installs from npm, from source or in Docker, and needs n8n on Node 20 or later with the API enabled. Configuration goes through an env file: the n8n API URL, the API key and a username and password for webhooks. It has tools for workflows and for executions, plus a section on integrating with assistants like Claude Desktop and VS Code through a JSON config. It documents the update path for each install method. MIT licensed.