io.github.ratamaha-git/n8n-mcp
NPM · @AUTOMATELAB/N8N-MCP · SCANNED SEP 21
MCP server for n8n: generate, lint, explain failed executions, drive live n8n via REST.
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
- 31 of 96 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 104 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1086 tokens (~120/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 io.github.ratamaha-git/n8n-mcp server?
io.github.ratamaha-git/n8n-mcp runs locally as an npm package, launched with npx -y @automatelab/n8n-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 · @automatelab/n8n-mcp
claude mcp add ratamaha-git-n8n-mcp -- npx -y @automatelab/n8n-mcp
{
"mcpServers": {
"ratamaha-git-n8n-mcp": {
"command": "npx",
"args": [
"-y",
"@automatelab/n8n-mcp"
]
}
}
} {
"servers": {
"ratamaha-git-n8n-mcp": {
"command": "npx",
"args": [
"-y",
"@automatelab/n8n-mcp"
]
}
}
} codex mcp add ratamaha-git-n8n-mcp -- npx -y @automatelab/n8n-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ratamaha-git-n8n-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@automatelab/n8n-mcp"
],
"enabled": true
}
}
} openclaw mcp add ratamaha-git-n8n-mcp --command npx --arg -y --arg @automatelab/n8n-mcp
mcp_servers:
ratamaha-git-n8n-mcp:
command: "npx"
args: ["-y", "@automatelab/n8n-mcp"] {
"McpServers": {
"ratamaha-git-n8n-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@automatelab/n8n-mcp"
]
}
}
} assistant mcp add ratamaha-git-n8n-mcp -t stdio -c npx -a -y @automatelab/n8n-mcp
{
"mcpServers": {
"ratamaha-git-n8n-mcp": {
"command": "npx",
"args": [
"-y",
"@automatelab/n8n-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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → 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 21 Sept 2026 · Analysed npm/@automatelab/n8n-mcp@0.3.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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 ~73
Activate or deactivate a workflow on a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Pass `active: false` to deactivate.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Defaults to true (activate). Set false to deactivate. |
| id | string | yes | Workflow ID. |
No output schema declared.
No examples provided.
n8n_create_workflow ~115
Create a workflow on a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Strips read-only fields (id, active, createdAt, ...) before posting. Workflows are created inactive — call n8n_activate_workflow afterward. Pairs with n8n_generate_workflow for end-to-end 'describe -> deploy'.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow | – | yes | Workflow JSON to create (typically the output of n8n_generate_workflow). Either a parsed object or a JSON string. |
No output schema declared.
No examples provided.
n8n_explain_execution ~164
Diagnose a failed or surprising n8n execution. Paste the execution JSON (from the n8n UI 'Show details' or `GET /executions/:id?includeData=true`); returns a per-node summary highlighting nodes that returned 0 items, unresolved `={{ ... }}` expressions, errors with hints, and LLM token usage. Hits the most common debugging pain point: items 'silently disappearing' between nodes.
| Name | Type | Req | Description |
|---|---|---|---|
| execution | – | yes | n8n execution object as either a parsed object or a JSON string. Accepts both the REST API shape (`{ data: { resultData: { runData, error, lastNodeExecuted } }, finished, status, ... }`) and the raw… |
No output schema declared.
No examples provided.
n8n_generate_workflow ~149
Generate a valid n8n workflow JSON from a plain-English description. Handles webhook/schedule/RSS triggers, common action nodes (Slack, Google Sheets, Discord, Gmail, Notion, HTTP), and AI Agent setups (LangChain root agent + chat model + memory + optional HTTP tool, wired with ai_languageModel / ai_memory / ai_tool connections). Returns workflow JSON with unique node IDs, connections, positions, and typeVersion on every node.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Plain-English workflow description, e.g. 'Stripe webhook -> Slack message + Google Sheets row'. |
| name | string | – | Optional workflow name. Derived from the first sentence of the description if omitted. |
No output schema declared.
No examples provided.
n8n_get_workflow ~72
Fetch a single workflow JSON by id from a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Returns the full nodes/connections payload — pair with n8n_lint_workflow to audit a deployed workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Workflow ID. |
No output schema declared.
No examples provided.
n8n_lint_workflow ~109
Lint an n8n workflow JSON. Returns concrete errors and warnings: missing credentials, deprecated node types (Function -> Code, spreadsheetFile -> convertToFile/extractFromFile), broken connections, missing or non-numeric typeVersion, duplicate node names or IDs, AI Agent missing ai_languageModel sub-node, Webhook missing webhookId, IF node still on v1 condition schema.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow | – | yes | n8n workflow as either a parsed object or a JSON string. |
No output schema declared.
No examples provided.
n8n_list_executions ~159
List recent executions from a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Filter by workflowId, status (success|error|waiting), limit. Pass `includeData: true` to get the full execution body (large) — pair with n8n_explain_execution to diagnose a specific failure.
| Name | Type | Req | Description |
|---|---|---|---|
| includeData | boolean | – | Include full execution data (large). Default false — pair with n8n_explain_execution. |
| limit | number | – | Page size (n8n default: 100, max: 250). |
| status | string | – | Filter by status: success | error | waiting. |
| workflowId | string | – | Filter by workflow ID. |
No output schema declared.
No examples provided.
n8n_list_workflows ~148
List workflows from a live n8n instance (requires N8N_API_URL + N8N_API_KEY env vars). Returns id, name, active, nodeCount, updatedAt, tags. Filter by active, tags, name. Use this when the user asks 'what workflows do I have?' or before n8n_get_workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Filter by active status. Omit to return both. |
| limit | number | – | Page size (n8n default: 100, max: 250). |
| name | string | – | Filter by exact workflow name. |
| tags | string | – | Comma-separated tag names to filter by. |
No output schema declared.
No examples provided.
n8n_scaffold_node ~97
Scaffold a TypeScript skeleton for an n8n custom node from a plain-English description. Returns a single TypeScript file implementing INodeType with description, credentials reference, and an execute method stub.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Plain-English description of what the node should do. |
| nodeName | string | – | Optional PascalCase node class name, e.g. 'DiscordRateLimited'. Derived from the description if omitted. |
No output schema declared.
No examples provided.
What is the io.github.ratamaha-git/n8n-mcp server?
io.github.ratamaha-git/n8n-mcp is listed in the public MCP registry as io.github.ratamaha-git/n8n-mcp. MCP server for n8n: generate, lint, explain failed executions, drive live n8n via REST. This page covers its npm package (@automatelab/n8n-mcp).
Is the io.github.ratamaha-git/n8n-mcp server safe to use?
io.github.ratamaha-git/n8n-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.ratamaha-git/n8n-mcp server expose?
io.github.ratamaha-git/n8n-mcp exposes 9 tools: n8n_scaffold_node, n8n_generate_workflow, n8n_lint_workflow, n8n_explain_execution, n8n_list_workflows, and 4 more. Their descriptions and schemas cost roughly 1,086 tokens of context every time the server is loaded.
Is the io.github.ratamaha-git/n8n-mcp server still maintained?
io.github.ratamaha-git/n8n-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.ratamaha-git/n8n-mcp server under?
io.github.ratamaha-git/n8n-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.