n8n's instance-level MCP server has been around for a few months, but until recently it could only run workflows you had already built. As of the late April update, it can build new workflows from a prompt and edit existing ones, directly inside your instance (per n8n's announcement). You point an MCP client at your instance, describe what you want, and the workflow appears in your n8n editor.

It works with any client that speaks MCP. Claude, ChatGPT, Cursor, and Windsurf are all named in n8n's post. It is first-party and built into every edition, including the free self-hosted Community Edition, so there is no separate service to run next to your instance. n8n recommends version 2.18.4 or higher for the build feature.

One point that causes confusion. This is the instance-wide MCP server, not the MCP Server Trigger node. The trigger node exposes a single workflow as a tool. The instance server lets a client see and operate across the workflows you enable (per n8n's docs).

How the build loop works

The interesting part is what happens after the prompt. The client does not just paste raw JSON into your instance. It generates the workflow, validates it, runs a test execution, reads any errors, and fixes itself before it returns the result to you. n8n says this loop is not scripted on their end. Most clients and models do it on their own.

Under the hood the server produces a TypeScript representation of the workflow rather than raw JSON, so the model has to write something that compiles before it touches your instance (per n8n's announcement). n8n reports this gives better results than direct JSON generation.

A small detail from their own testing. A coding agent like Claude Code gave better results than a chat client with the same prompt and the same model.

The limits

It ships as a public preview, and n8n is open about the current limits. Complex branching and heavy conditional logic often need manual cleanup. The model sometimes picks the wrong node when several could do the same job, so if you name the exact node or service you want, it helps a lot. You also have to enable MCP at the instance level and then enable each workflow you want a client to reach. Every connected client sees every workflow you have enabled, since you cannot restrict specific workflows to specific clients (per n8n's docs).

If you have used the native MCP server, how much did you have to fix by hand on a workflow with several conditional branches?