Self-Hosting n8n and Letting Claude Build the Workflows

Description and use

The author self‑hosted n8n in Docker, registered it as an MCP server, and used Claude to programmatically build three workflows, eliminating manual canvas work and reducing configuration errors.

Problem

Automating workflow creation in n8n via Claude while self-hosting the platform, avoiding manual canvas construction and handling environmental pitfalls.

Outcome

Three production‑ready workflows built entirely by Claude, eliminating manual canvas work and reducing configuration errors.

Workflow

• Register n8n Docker container with MCP server
• Configure .claude.json to point to local n8n instance
• Use Claude to: get_sdk_reference, search_nodes, create_workflow_from_code, update_workflow(operations)
• Iteratively build and test workflows
• Deploy and monitor workflows

Evidence

I ran n8n in Docker on my own machine, registered it with Claude Code as an MCP server, and then built three real workflows by describing them to the agent, which created and edited the nodes programmatically.

Source

Action nodes silently clobber $json.

Source

n8n in Docker cannot reach your host's Ollama at localhost.

Source