n8n Manager MCP
NPM · N8N-MANAGER-MCP
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI.
Available components
Last scanned (10 hours ago)
Scores higher than 45% of npm servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 877 tokens (~62/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "n8n_delete_workflow" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/n8n-manager-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
n8n_activate_workflow ~63
Activate or deactivate an n8n workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | true to activate, false to deactivate |
| server_name | string | – | Server name. Uses default if omitted. |
| workflow_id | string | yes | n8n workflow ID |
No output schema declared.
No examples provided.
n8n_add_server ~112
Add or update an n8n server connection. The API key can be created in n8n under Settings > API.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | n8n API key (from Settings > API in n8n) |
| is_default | boolean | – | Set as default server |
| name | string | yes | Server name (e.g. 'production', 'staging') |
| url | string | yes | n8n server URL (e.g. 'http://localhost:5678') |
No output schema declared.
No examples provided.
n8n_create_workflow ~88
Create a new n8n workflow. Provide the full workflow JSON including nodes and connections.
| Name | Type | Req | Description |
|---|---|---|---|
| activate | boolean | – | Activate workflow after creation |
| connections | array | – | Array of connections between nodes |
| name | string | yes | Workflow name |
| nodes | array | yes | Array of workflow nodes |
| server_name | string | – | Server name. Uses default if omitted. |
No output schema declared.
No examples provided.
n8n_delete_workflow ~58
Delete a workflow from an n8n server. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Server name. Uses default if omitted. |
| workflow_id | string | yes | n8n workflow ID to delete |
No output schema declared.
No examples provided.
n8n_describe_nodes ~43
Get information about common n8n node types. Useful for understanding which nodes to use when building workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
No output schema declared.
No examples provided.
n8n_export_workflow ~70
Export a workflow from an n8n server as JSON. Returns the complete workflow definition that can be imported into another n8n instance.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Server name. Uses default if omitted. |
| workflow_id | string | yes | n8n workflow ID to export |
No output schema declared.
No examples provided.
n8n_get_workflow ~59
Get detailed information about a specific n8n workflow including all nodes, connections, and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Server name. Uses default if omitted. |
| workflow_id | string | yes | n8n workflow ID |
No output schema declared.
No examples provided.
n8n_import_workflow ~80
Import a workflow JSON onto an n8n server. Takes a full n8n workflow JSON and creates it on the server.
| Name | Type | Req | Description |
|---|---|---|---|
| activate | boolean | – | Activate after import |
| server_name | string | – | Target server name. Uses default if omitted. |
| workflow_json | string | yes | Complete n8n workflow JSON as string |
No output schema declared.
No examples provided.
n8n_list_executions ~78
List recent workflow executions on an n8n server. Shows status, timing, and errors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| server_name | string | – | Server name. Uses default if omitted. |
| status | string | – | Filter by status |
| workflow_id | string | – | Filter by workflow ID |
No output schema declared.
No examples provided.
n8n_list_servers ~20
List all configured n8n server connections.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
n8n_list_workflows ~65
List all workflows on an n8n server. Returns workflow names, IDs, active status, and node counts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of workflows to return |
| server_name | string | – | Server name from config. Uses default if omitted. |
No output schema declared.
No examples provided.
n8n_ping_server ~36
Test the connection to an n8n server.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Server name. Uses default if omitted. |
No output schema declared.
No examples provided.
n8n_remove_server ~35
Remove an n8n server from the configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | yes | Name of the server to remove |
No output schema declared.
No examples provided.
n8n_update_workflow ~70
Update an existing n8n workflow. Send the full updated workflow JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Server name. Uses default if omitted. |
| workflow_id | string | yes | n8n workflow ID to update |
| workflow_json | string | yes | Full workflow JSON as string |
No output schema declared.
No examples provided.
How do I install the n8n Manager MCP server?
n8n Manager MCP runs locally as an npm package, launched with npx -y n8n-manager-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · n8n-manager-mcp
claude mcp add lukisch-n8n-manager-mcp -- npx -y n8n-manager-mcp
What is the n8n Manager MCP server?
n8n Manager MCP is listed in the public MCP registry as io.github.lukisch/n8n-manager-mcp. MCP server for n8n workflow management -- view, create, sync and manage workflows via AI. This page covers its npm package (n8n-manager-mcp).
Is the n8n Manager MCP server safe to use?
n8n Manager MCP scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the n8n Manager MCP server expose?
n8n Manager MCP exposes 14 tools: n8n_list_workflows, n8n_get_workflow, n8n_create_workflow, n8n_update_workflow, n8n_delete_workflow, and 9 more. Their descriptions and schemas cost roughly 877 tokens of context every time the server is loaded.
Is the n8n Manager MCP server still maintained?
n8n Manager MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the n8n Manager MCP server under?
n8n Manager MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.