n8n + Claude via MCP: an agent that builds its own automations
Connect Claude to n8n through ReDock's MCP tools and let an agent draft, wire, and test workflows on your Mac, no API keys, no cloud.
You can point Claude — or Claude Code, Cursor, or any MCP client — at n8n running on your Mac and have it help build the automations for you. ReDock exposes its whole app as MCP tools on localhost:47200, and n8n is one of the stacks it runs. That means an agent can read what’s on your machine, spin up an n8n instance, and talk you through wiring a workflow, all against a real local runtime with real HTTPS.
Why MCP changes how you build workflows
The Model Context Protocol is a standard way for AI clients to call tools running on your machine. Instead of an agent guessing at your setup, it calls a tool, gets a structured answer, and acts on it. We wrote up the basics in what is MCP, and the connection steps in the MCP docs.
For automation, the payoff is concrete. Building an n8n flow means knowing the trigger, the nodes in between, the credentials each node needs, and the shape of the data flowing through. That’s a lot of context to hold. An agent connected over MCP can see the site is running, know it has a real .test domain, and reason about the flow with you instead of at you.
What the agent can actually do
ReDock is a free (alpha) native macOS app. Once you connect a client to its MCP endpoint, the agent works against the stacks you run — WordPress, headless WP, Astro, Next.js, Node, Bun, PHP, MySQL, plus n8n and Remotion. For n8n specifically:
- See the running instance. The agent can confirm n8n is up, on which
.testdomain, and reachable over HTTPS — not guess. - Reason about triggers and nodes. Describe the outcome you want (“new WordPress post → summarize → post to Slack”), and the agent proposes the node chain and the credentials each step needs.
- Draft the workflow JSON. n8n workflows are JSON. An agent is good at JSON. You review, import, and run it inside n8n.
- Test against real webhooks. With sharing on, ReDock opens a Cloudflare tunnel, so the agent can help you verify a webhook actually arrives — covered in webhooks on localhost.
ReDock also ships a built-in agent and a local-LLM catalog, so you can run this without any API keys at all — see the built-in agent docs.
A concrete first pass
Say you want a daily digest of your site’s new comments. The conversation looks like: you describe it, the agent confirms your n8n site is running, proposes a cron trigger plus an HTTP node hitting your WordPress REST API plus a formatting step plus an email node, and hands you workflow JSON. You import it in n8n’s UI, add your email credential, and run once to check. If the shape is wrong, you tell the agent what came back and it adjusts.
The agent doesn’t replace n8n’s visual editor — it gets you to a working first draft faster, and it explains the parts you don’t know yet. You still own and understand the flow.
Local-first, no keys required
Because everything runs on your Mac, the sensitive parts stay there. Your n8n credentials live in your local instance. Your data flows through your hardware. If you use ReDock’s built-in agent with a local model from its catalog, there’s no external API call at all — the model runs on your machine.
If you’d rather use Claude Desktop or Claude Code, those connect to the same MCP endpoint. The tools are identical; only the client differs. The one-click n8n setup is the same either way — see n8n on your Mac, one click.
FAQ
Do I need an API key to have an agent build n8n workflows?
No. ReDock includes a built-in agent and a local-LLM catalog that runs models on your Mac, so you can build workflows with no keys and no cloud calls. You can also connect Claude or Cursor if you prefer those clients.
Does the agent run inside n8n?
No. The agent connects over MCP to ReDock and helps you assemble the workflow — proposing nodes and drafting the JSON. You import and run it in n8n’s own editor, so you stay in control of what executes.
Which clients can connect?
Any MCP client: Claude Desktop, Claude Code, Cursor, or others. They all talk to ReDock’s endpoint on localhost:47200. See the MCP docs for setup.
An agent that can see your machine builds better automations than one that can’t. Download ReDock and connect your first client today.