# N8n (npm · @pipeworx/mcp-n8n)

n8n MCP — query your own n8n instance (BYO).

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-n8n/n8n-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-n8n/n8n-mcp)
- npm · `@pipeworx/mcp-n8n`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n.md), [page](https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-n8n`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-n8n).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 746 tokens (~248/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the N8n MCP server?

N8n runs locally as an npm package, launched with npx -y @pipeworx/mcp-n8n. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-n8n -- npx -y @pipeworx/mcp-n8n
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n8n"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n8n"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-n8n -- npx -y @pipeworx/mcp-n8n
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-n8n": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-n8n"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-n8n --command npx --arg -y --arg @pipeworx/mcp-n8n
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-n8n:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-n8n"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-n8n": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-n8n"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-n8n -t stdio -c npx -a -y @pipeworx/mcp-n8n
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n8n"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `n8n_list_workflows` (~246 tokens)

List workflows in YOUR n8n instance, with an active/inactive breakdown. Answers "how many active workflows do we have", "list our n8n workflows", "which workflows are turned on". Each workflow: id, name, active (on/off), createdAt, updatedAt, tags. Set active_only:true to list just the live ones. Requires your instance_url + n8n API key (_apiKey).

Input parameters:

- `_apiKey` (string, required): REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack.
- `active_only` (boolean): Only return active (turned-on) workflows. Default false (all).
- `instance_url` (string, required): REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL.
- `limit` (number): Max workflows to fetch (1-250, default 100).

### `n8n_get_workflow` (~195 tokens)

Get one workflow's detail by id from your n8n instance — name, active state, node list (which integrations it uses), tags, timestamps. Get the id from n8n_list_workflows. Requires your instance_url + n8n API key (_apiKey).

Input parameters:

- `_apiKey` (string, required): REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack.
- `instance_url` (string, required): REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL.
- `workflow_id` (string, required): The workflow id — from n8n_list_workflows.

### `n8n_list_executions` (~251 tokens)

List recent workflow executions (runs) in your n8n instance — for "did our workflows run", "show recent failures", "execution history". Each: id, workflowId, status (success/error/waiting), mode, startedAt, stoppedAt. Filter by status and/or workflow_id. Requires your instance_url + n8n API key (_apiKey).

Input parameters:

- `_apiKey` (string, required): REQUIRED — your n8n API key (Settings → n8n API → Create an API key). Sent as the X-N8N-API-KEY header. No shared key exists for this pack.
- `instance_url` (string, required): REQUIRED — your n8n instance base URL, e.g. "https://you.app.n8n.cloud" (n8n Cloud) or "https://n8n.example.com" (self-hosted). Must be a public https URL.
- `limit` (number): Max executions (1-250, default 50).
- `status` (string): Filter: "success" | "error" | "waiting". Omit for all.
- `workflow_id` (string): Only executions of this workflow id.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 66
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the N8n MCP server?

N8n is an MCP server listed in the public MCP registry as io.github.pipeworx-io/n8n. n8n MCP, query your own n8n instance (BYO). This page covers its npm package (@pipeworx/mcp-n8n).

### Is the N8n MCP server safe to use?

N8n scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 MCP server expose?

N8n exposes 3 tools: n8n_list_workflows, n8n_get_workflow, n8n_list_executions. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.

### Is the N8n MCP server still maintained?

N8n 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 MCP server under?

N8n declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-n8n
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-n8n
- Repository: https://github.com/pipeworx-io/mcp-n8n
- Website: https://pipeworx.io/packs/n8n
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-n8n/pipeworx-mcp-n8n