How to Connect Claude Code to n8n (For Free, Without a Course)

My AI minions just leveled up again. This time, they learned how to build n8n workflows for me. One step closer to world domination… but first, too many meetings.

Here’s the backstory. I watched a YouTube video about connecting Claude Code to n8n using MCP (Model Context Protocol), and it genuinely looked transformative. The creator walked through the concept, showed impressive results, and then said the magic words: “Check the link in the description for all the resources you need.”

So I did. And it was behind a paywall.

No big deal. Happens sometimes. I found another creator covering the same topic. Same promise. Same paywall. Then a third. Same thing. At this point I was three creators deep into the exact same bait-and-switch, and the frustration wasn’t about the money. It was about the pattern. These are open-source tools on public GitHub repos. The information is free. The creators just packaged it behind a gate and made it sound like you need their course to figure it out.

You don’t.

Here’s the part where I admit something embarrassing. After hitting the third paywall, I finally thought to just ask Claude to find the actual repos for me. That should have been step two, not step four. I literally have an AI assistant that can search the internet, and I burned 30 minutes clicking through YouTube descriptions instead. Sometimes the cobbler’s kids really do go barefoot.

Anyway. Claude found everything in about 90 seconds, I had it configured in under 15 minutes, and it transformed my entire workflow the next day. So here’s the full setup guide with every link you need. No paywall. No course. No “premium Discord.”

What This Does

When you connect Claude Code to n8n through MCP, Claude gains deep knowledge of over 1,000 n8n nodes, including their properties, operations, required parameters, and real-world configuration patterns. Instead of you manually dragging nodes around the n8n canvas and guessing at parameter names, you describe what you want in plain English and Claude builds the workflow for you.

Before this setup, asking Claude to build an n8n workflow was a guessing game. It would get node names wrong, use incorrect parameter formats, and produce workflows that looked reasonable but failed on execution. With MCP connected, Claude can query the actual node documentation in real time, validate configurations before deployment, and pull from thousands of real-world template examples. The difference isn’t incremental. It’s the difference between “this might work” and “this works.”

What You Need Before You Start

You need three things already in place before this setup makes sense.

First, a working and up-to-date n8n instance. This can be self-hosted or n8n Cloud. If you’re running n8n locally, it’s typically at http://localhost:5678. If you’re on a cloud or hosted instance, you’ll use that URL instead. And when I say up to date, I mean actually up to date. I was one version behind because (like every true techie) I’m great at telling clients to keep their systems current and terrible at doing it myself. The MCP server worked fine, but the workflows Claude built kept throwing errors that made no sense until I finally updated n8n and everything clicked. Save yourself the troubleshooting spiral. Update first.

Second, Claude Code installed and working. Claude Code is Anthropic’s command-line tool for agentic coding. If you haven’t set it up yet, that’s a separate process. Get that working first, then come back here.

Third, Node.js installed on your machine. The MCP server runs on Node, so you’ll need it available. Most developers already have this, but if you don’t, grab it from nodejs.org.

Step 1: Generate Your n8n API Key

The MCP server needs API access to your n8n instance. Here’s how to create that key.

Log into your n8n instance
Click on your user icon in the bottom-left corner
Go to Settings
Select n8n API from the left sidebar
Click Create an API key
Give it a label (something like “Claude Code MCP”) and set your preferred expiration
Copy the key immediately. You won’t be able to see it again

Keep this key somewhere secure. You’ll need it in the next step.

Step 2: Add the n8n-MCP Server to Claude Code

This is the core connection. The n8n-MCP server (created by Romuald Członkowski) provides Claude with structured access to n8n’s node documentation, properties, and operations.

Open your terminal and run:

claude mcp add n8n-mcp --scope user -- npx n8n-mcp

Claude Code will prompt you for environment variables. You’ll need to set:

N8N_API_URL: Your n8n instance URL (e.g., http://localhost:5678 or your cloud URL)
N8N_API_KEY: The API key you just created

Alternatively, you can create or edit your .mcp.json file directly. If you want the server available across all your projects (user scope), place this in your home directory’s Claude config. For project-specific use, add it to your project root:

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["n8n-mcp"],
      "env": {
        "MCP_MODE": "stdio",
        "LOG_LEVEL": "error",
        "DISABLE_CONSOLE_OUTPUT": "true",
        "N8N_API_URL": "http://localhost:5678",
        "N8N_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace the URL and API key with your actual values.

To verify the connection is working, start Claude Code and run the /mcp command. You should see the n8n-mcp server listed with its available tools.

GitHub repo: github.com/czlonkowski/n8n-mcp

Step 3: Install the n8n Skills Plugin

The MCP server gives Claude the raw knowledge. The skills plugin teaches Claude how to use that knowledge well. It’s a set of seven complementary skills covering expression syntax, workflow patterns, node configuration, validation, and code patterns. Think of it as the difference between giving someone a dictionary versus teaching them how to write.

In Claude Code, run:

/plugin install czlonkowski/n8n-skills

That’s it. The skills activate automatically when Claude detects relevant queries. When you ask Claude to build a webhook workflow, the workflow patterns skill kicks in. When you’re debugging a validation error, the validation expert skill takes over. They compose together seamlessly.

The seven skills cover:

Expression Syntax: Correct n8n expression patterns and common mistakes (like webhook data living under $json.body, not $json)
MCP Tools Expert: How to use the MCP tools effectively, which is the highest priority skill
Workflow Patterns: Five proven architectural patterns drawn from thousands of real templates
Validation Expert: Interpreting validation errors and fixing them without getting stuck in loops
Node Configuration: Operation-aware setup guidance, including property dependencies
Code JavaScript: Writing effective JavaScript in n8n Code nodes with correct return formats
Code Python: Python patterns with honest documentation of limitations (spoiler: use JavaScript for 95% of use cases)

GitHub repo: github.com/czlonkowski/n8n-skills

Step 4: Test It

Start a new Claude Code session and try something simple:

“Build me an n8n workflow that triggers on a webhook, checks if the incoming data has an email field, and sends a Slack notification with the email address.”

Watch what happens. Claude will search for the right nodes using the MCP tools, pull their actual properties and required parameters, build the workflow with correct connections, and validate it before handing it to you. No guessing. No made-up parameter names. No “this should work, probably.”

If you want to see the MCP tools in action during the conversation, use the /mcp command to check server status and available tools.

What Changed for Me

I set this up on a Monday. By Tuesday, I had built more n8n workflows in a single day than I normally build in two weeks. The friction wasn’t gone. You still need to understand what you’re trying to automate and why. But the mechanical parts, the “what’s this node called” and “what parameters does it need” and “why is this connection failing,” all of that disappeared.

The real shift is confidence. When Claude builds a workflow with MCP connected, it’s working from actual documentation, not training data that might be outdated. It validates configurations before you deploy them. When something fails, it can look up the error context and fix it intelligently instead of just guessing at a different configuration.

For MSPs and IT teams running n8n as part of their automation stack, this is a significant force multiplier. Your automation engineer doesn’t need to memorize 1,000+ node configurations anymore. They need to know what problem they’re solving, and Claude handles the implementation details.

The Paywall Problem

I’m not going to name the creators whose courses I clicked through. This isn’t about individual people. It’s a pattern across the tech content space right now. Someone discovers an open-source tool, makes a video showing how powerful it is, and then locks the actual setup instructions behind a paid course or community. The video functions as a commercial for the course, not as educational content.

The irony is thick. These tools are open source. The repos are public. The documentation is free. The creators are essentially charging you for the convenience of not having to find publicly available information yourself.

Or, you know, you could just ask your AI assistant to find it. Which is what I should have done after the first paywall instead of the third.

Resources

Everything you need is right here:

n8n-MCP Server: github.com/czlonkowski/n8n-mcp. The MCP server that gives Claude knowledge of 1,084 n8n nodes
n8n Skills Plugin: github.com/czlonkowski/n8n-skills. Seven complementary skills for building production-ready workflows
n8n API Documentation: docs.n8n.io/api/authentication. Official docs for API key setup
Claude Code: Available through Anthropic for paid Claude subscribers

All free. All public. No paywall required.