# N8n Multi Instance

Use when an n8n-mcp account targets more than one n8n instance, i.e.

- Repository: https://github.com/czlonkowski/n8n-mcp (23187 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add czlonkowski/n8n-mcp --skill n8n-multi-instance -g -a claude-code -y`
Codex: `npx skills add czlonkowski/n8n-mcp --skill n8n-multi-instance -g -a codex -y`
Cursor: `npx skills add czlonkowski/n8n-mcp --skill n8n-multi-instance -g -a cursor -y`
Gemini CLI: `npx skills add czlonkowski/n8n-mcp --skill n8n-multi-instance -g -a gemini-cli -y`

## Description

Use when an n8n-mcp account targets more than one n8n instance, i.e. the `n8n_instances` tool is available, the user mentions multiple n8n instances or environments (prod vs staging, several teams or clients), a workflow / datatable / credential / execution call returns an unexpected NOT_FOUND or reads data you don't recognize, or a credential create/update/delete is refused with an `INSTANCE_AMBIGUOUS` error. Covers choosing and switching which instance this MCP session targets, verifying the target before high-stakes work, credential writes above all, and recovering from misroutes and ambiguous-write fail-closes. Always consult this skill before operating on a specific instance, before any credential create/update/delete on a multi-instance account, or when a call hits the wrong/empty data or an `INSTANCE_AMBIGUOUS` error.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Working with multiple n8n instances over MCP

When the `n8n_instances` tool is available, the user has **multi-instance mode** on: one MCP
connection can reach several n8n instances (e.g. `prod`, `staging`, or one per client/team).
Every other n8n tool (`n8n_get_workflow`, `n8n_list_workflows`, `n8n_update_partial_workflow`,
`n8n_manage_datatable`, `n8n_manage_credentials`, `n8n_executions`, `n8n_test_workflow`, …) runs
against **whichever instance this session is currently targeting**. There is no per-call instance
argument: you change the target only by switching. Target the wrong instance and a read returns the
wrong data and a write lands in the wrong place, usually with **no error** (the one exception is an
ambiguous credential write, which fails closed; see below). So target deliberately.

If the `n8n_instances` tool is **not** present, the account is single-instance: ignore this skill
and use the n8n tools directly.

## Golden rules

Six rules. Each prevents a class of silent misroute.

The rest: https://github.com/czlonkowski/n8n-mcp/blob/HEAD/data/skills/n8n-multi-instance/SKILL.md