Server facts
n8n MCP Server
Project
- Author
- leonardsellem
- Repository
- github.com/leonardsellem/n8n-mcp-server
- License
- MIT
- Category
- Productivity
Tech
- Runtime / language
- nodeJavaScript
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 1,631
- Last commit
- Data as of
Tags
- Execution Management
- N8n
- Webhooks
- Workflow Automation
Overview
n8n MCP Server connects AI assistants to an n8n instance so they can manage automation workflows through MCP. Its tool set covers listing and inspecting workflows, creating and updating definitions, deleting workflows, and changing activation state. Execution tools can start a workflow through the API, inspect a particular run, list runs associated with a workflow, or stop a running execution. MCP resources provide browsable workflow and execution information alongside those tools. This combination supports both changing an automation and checking what happened when it ran.
A separate webhook path triggers an n8n workflow by name and passes data to it. The README instructs users to create a webhook-triggered workflow, configure Basic Authentication on its webhook node, and supply matching webhook credentials to the server. Standard API operations instead use an n8n API URL including /api/v1 and an API key with appropriate permissions. Local prerequisites are Node.js 20 or newer and an API-enabled n8n instance. Installation options include a global npm package, a source build, and Docker. The assistant configuration can run the globally installed executable or a built JavaScript entry point at an absolute path. Source installations need a build before that entry point exists, and updates require restarting the server. The project describes itself as community-driven and maintained part-time while seeking additional maintainers.
Install & configure
Requirements
- Node.js 20 or newer
- An n8n instance with API access enabled
- The globally installed @leonardsellem/n8n-mcp-server package
- An n8n API key
n8n-mcp-serverInstall with npm install -g @leonardsellem/n8n-mcp-server before using this executable. N8N_WEBHOOK_USERNAME and N8N_WEBHOOK_PASSWORD are needed only for webhook tools. Source builds and Docker are documented alternatives.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"n8n-mcp-server": {
"command": "n8n-mcp-server",
"args": [],
"env": {
"N8N_API_URL": "<Full n8n API URL including /api/v1>",
"N8N_API_KEY": "<n8n API key with appropriate permissions>"
}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"n8n-mcp-server": {
"command": "n8n-mcp-server",
"args": [],
"env": {
"N8N_API_URL": "<Full n8n API URL including /api/v1>",
"N8N_API_KEY": "<n8n API key with appropriate permissions>"
}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"servers": {
"n8n-mcp-server": {
"type": "stdio",
"command": "n8n-mcp-server",
"args": [],
"env": {
"N8N_API_URL": "<Full n8n API URL including /api/v1>",
"N8N_API_KEY": "<n8n API key with appropriate permissions>"
}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"n8n-mcp-server": {
"command": "n8n-mcp-server",
"args": [],
"env": {
"N8N_API_URL": "<Full n8n API URL including /api/v1>",
"N8N_API_KEY": "<n8n API key with appropriate permissions>"
}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"n8n-mcp-server": {
"type": "stdio",
"command": "n8n-mcp-server",
"args": [],
"env": {
"N8N_API_URL": "<Full n8n API URL including /api/v1>",
"N8N_API_KEY": "<n8n API key with appropriate permissions>"
}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| workflow_list | Enumerate workflows in the connected n8n instance. |
| workflow_get | Read one workflow’s configuration and details. |
| workflow_create | Create a workflow definition. |
| workflow_update | Change an existing workflow definition. |
| workflow_delete | Remove a workflow. |
| workflow_activate | Enable a workflow. |
| workflow_deactivate | Disable a workflow. |
| execution_run | Start a workflow through the n8n API. |
| run_webhook | Trigger a named workflow through its webhook. |
| execution_get | Inspect details for a specific workflow run. |
| execution_list | List runs associated with a workflow. |
| execution_stop | Stop an execution that is currently running. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Create and update n8n workflows from an AI assistant.
- Activate or deactivate existing automations.
- Run workflows and inspect their execution results.
- Trigger a Basic-Auth-protected n8n webhook by workflow name.
Strengths
- Covers workflow lifecycle management and execution control.
- Supports both API-triggered and webhook-triggered runs.
- Provides MCP resources as well as actionable tools.
Limitations
- Requires an API-enabled n8n instance and suitable API credentials.
- Webhook use needs a configured workflow and Basic Authentication credentials.
- The README describes part-time maintenance and a search for co-maintainers.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
