n8n Manager MCP
NPM · N8N-MANAGER-MCP · SCANNED SEP 20
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 48 of 149 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 0 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 1177 tokens (~65/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 18 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
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 ellmos-ai-n8n-manager-mcp -- npx -y n8n-manager-mcp
{
"mcpServers": {
"ellmos-ai-n8n-manager-mcp": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
} {
"servers": {
"ellmos-ai-n8n-manager-mcp": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
} codex mcp add ellmos-ai-n8n-manager-mcp -- npx -y n8n-manager-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ellmos-ai-n8n-manager-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"n8n-manager-mcp"
],
"enabled": true
}
}
} openclaw mcp add ellmos-ai-n8n-manager-mcp --command npx --arg -y --arg n8n-manager-mcp
mcp_servers:
ellmos-ai-n8n-manager-mcp:
command: "npx"
args: ["-y", "n8n-manager-mcp"] {
"McpServers": {
"ellmos-ai-n8n-manager-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"n8n-manager-mcp"
]
}
}
} assistant mcp add ellmos-ai-n8n-manager-mcp -t stdio -c npx -a -y n8n-manager-mcp
{
"mcpServers": {
"ellmos-ai-n8n-manager-mcp": {
"command": "npx",
"args": [
"-y",
"n8n-manager-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 13 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/n8n-manager-mcp@0.1.13
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 →
Dependencies 149 packages
| Packages resolved | 149 |
|---|---|
| Stale | 48 |
| 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 ~63
Delete a workflow from an n8n server. By default, a JSON backup is saved before deletion.
| 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_backups ~58
List local workflow backups created before n8n mutations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum backups to show. |
| server_name | string | – | Optional server name filter. |
| workflow_id | string | – | Optional workflow ID filter. |
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_restore_workflow ~109
Restore a workflow from a local backup. By default creates a new workflow; pass target_workflow_id to overwrite an existing workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| activate | boolean | – | Activate restored workflow after restore. |
| backup_path | string | yes | Path returned by n8n_list_backups or mutation output. |
| server_name | string | – | Target server name. Uses default if omitted. |
| target_workflow_id | string | – | Existing workflow ID to overwrite. If omitted, creates a new workflow. |
No output schema declared.
No examples provided.
n8n_safety_status ~28
Show n8n Manager safety settings, backup directory, and audit log location.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
n8n_set_safety_mode ~100
Configure local safety settings: read-only mode, backup-before-mutation, and audit logging.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_log | boolean | – | When true, appends mutation outcomes to ~/.n8n-manager-mcp/audit.log. |
| backup_before_mutations | boolean | – | When true, exports workflows before update/delete/activate/restore. |
| read_only | boolean | – | When true, blocks create/update/delete/activate/import/restore operations. |
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.
What is the n8n Manager MCP server?
n8n Manager MCP is listed in the public MCP registry as io.github.ellmos-ai/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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 18 tools: n8n_safety_status, n8n_set_safety_mode, n8n_list_workflows, n8n_get_workflow, n8n_create_workflow, and 13 more. Their descriptions and schemas cost roughly 1,177 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 20 September 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.