n8n Multi-Instance is a skill for Claude that applies when one n8n-mcp account reaches more than one n8n instance, such as production and staging or one per client. It shows how to name the target with the instance argument on every call and when the n8n_instances switch mode is worth using.
It also covers the error codes INSTANCE_NOT_FOUND and INSTANCE_AMBIGUOUS, why credential writes need an explicit instance, how to recover when an unexpected NOT_FOUND means a wrong target, and how to copy a workflow or credential between instances.
What You Get
- Six golden rules for targeting: list first, name the instance, never guess and treat NOT_FOUND as a misroute
- The behaviour of the instance argument, including that it never changes the default
- The n8n_instances list and switch shapes and a table of its error codes
- A recovery playbook mapping symptoms such as empty data or INSTANCE_AMBIGUOUS to fixes
- Credential rules: name the instance on every create, update and delete
- A step list for copying a workflow or credential from one instance to another
Common Use Cases
- Running work on production and staging from one connection
- Several agents or chats using the same n8n-mcp account in parallel
- Creating a credential on the correct client’s instance
- Working out why a known workflow returns NOT_FOUND
- Copying a workflow from staging to production
What Makes It Unique
It addresses a failure that produces plausible data from the wrong place, and it explains how a switch made in one chat moves every other chat on a hosted connection. Its rule to name the instance on each call removes the shared default from the picture, and it adds a fail-closed path for secret writes.
Under The Hood
The skill is instructions only, with no scripts or reference files. It tells Claude to call the n8n_instances tool and to pass an instance name on n8n-mcp calls that read workflows, executions, datatables and credentials or write them. Those calls go to the n8n server you registered. It can create, update or delete workflows and credentials on the named instance, so it asks Claude to confirm the target name before secret writes.