Agent skill · software engineering · sickn33
n8n-multi-instance
Select, verify, and safely switch n8n MCP instances across production, staging, teams, or clients, especially before credential writes.
Why this skill is useful
Adds specific workflows and safety checks for managing multiple n8n instances that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Working with multiple n8n instances over MCP When to Use Use this skill whenever one MCP connection can target multiple n8n instances, before instance-specific reads or writes, and whenever results suggest the session is aimed at the wrong environment. Resolve the target by stable instance ID, verify it with a read-only health check, and state the resolved environment before mutations. Require explicit confirmation for credential create/update/delete operations, never print secret values, and stop on ambiguous targeting rather than guessing. When the n8ninstances 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 (n8ngetworkflow, n8nlistworkflows, n8nupdatepartialworkflow, n8nmanagedatatable, n8nmanagecredentials, n8nexecutions, n8ntestworkflow, …) 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 n8ninstances 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. 1. Discover first. Call n8ninstances({mode:"list"}) before acting so you know the instance names and which one is current. 2. Switch by name to your target before doing work on a non-default instance: n8ninstances({mode:"switch", name:"<instance name>"}). The match is case-insensitive. 3. Switch in its own turn. Never put a switch and a dependent operation in the same parallel tool-call batch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/n8n-multi-instance--333463