Building in n8n with Claude

#claude #n8n #ai #mcp

n8n raised $180M at a $2.5B valuation last October. Their pitch calls it an "AI-first automation platform," and founder Jan Oberhauser describes it as "the Excel of AI."

I've always been a "code-first" guy. But with the ecosystem shifting toward n8n as the "brain" for AI automations, I wanted to see if it's a legitimate production tool or just a fancy playground for drawing boxes.

GitHub: r-ms/n8n-mcp | 20 tools | MIT | Claude Code / Desktop / Cursor

The use case

I follow ~30 YouTube channels on AI research and engineering. 90% of uploads are fluff. I needed a system that monitors channels, extracts transcripts, scores relevance with an LLM, and delivers a 30-second brief to Telegram every morning.

Why n8n and not a Python script?

Sure, Claude writes the script in 20 minutes. But then you need monitoring, alerting, logging, restart logic, state management. Claude can write all of that too — but now you're spending hours on infrastructure instead of the product.

n8n solves the ops around the code: visual execution traces (what went into the LLM, what came out), OAuth/retry/state management out of the box.

The "UI Gap"

I wanted Claude to build for me via n8n's API. But n8n's UI does a massive amount of invisible heavy lifting the API doesn't:

Missing Defaults: Code Node v2 requires a language parameter the UI sets automatically. Omit it via API — silent break.

Version Drift: SplitInBatches v3 swapped its output ports. Wrong version = infinite loop.

The Trailing Space: Two hours debugging a 404. The API had created a webhook URL with a trailing space from my prompt. The UI would have trimmed it.

The MCP

I built an MCP to bridge the gap. 20 tools for n8n, plus a know-how database and auto-fix rules. When Claude creates a workflow, the MCP intercepts it:

Validates node versions
Auto-injects missing UI-default parameters
Fixes naming conventions before they break webhook routing

Claude gets the full context of the n8n instance and debugs execution errors by reading JSON logs directly.

Full list of 7 auto-fix rules and 11 knowhow entries in the README.

From Low-Code to Agentic-Code

The canvas is becoming a debugger, not an editor.

Drawing lines between boxes is just another way of manually managing complexity — with a mouse instead of a keyboard. In the Agentic era, humans manage the intent. The agent manages the structural complexity. n8n's role shifts from "design tool" to "reliable runtime" — the engine that ensures intent is executed and logged.

The visual canvas remains, but as an audit trail. It's where you verify what the agent built, not where you build.

Try it

git clone https://github.com/r-ms/n8n-mcp.git
cd n8n-mcp && npm install && npm run build

{
  "mcpServers": {
    "n8n": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/n8n-mcp/dist/index.js"],
      "env": {
        "N8N_API_URL": "http://localhost:5678",
        "N8N_API_KEY": "your-api-key"
      }
    }
  }
}