n8n MCP Server: Connect n8n to Claude and AI Agents (2026 Guide)

What Is the n8n MCP Server?

n8n is a workflow automation tool that now speaks the Model Context Protocol natively. That means an AI agent like Claude can call your n8n workflows the same way it calls any other MCP tool.

Before this existed, connecting n8n to an LLM meant webhooks and custom glue. You wrote an endpoint, described it by hand, and hoped the model called it right.

MCP removes that friction. n8n exposes a standard, self-describing tool surface, and any MCP client discovers it automatically.

If MCP itself is new to you, read What Is the Model Context Protocol? first — this guide assumes you know what a tool call is.

n8n ships two dedicated MCP nodes, and most confusion comes from mixing them up. Let me draw the line clearly.

Two Directions: Server vs Client

n8n can sit on either side of an MCP connection. Which node you reach for depends on who is calling whom.

MCP Server Trigger = n8n exposes tools outward. MCP Client Tool = n8n consumes tools from elsewhere. That single distinction unlocks the rest of this guide.

n8n as an MCP Server (MCP Server Trigger)

The MCP Server Trigger node turns a workflow into a live MCP endpoint.

Drop the node onto a canvas and it gives you a URL — a Streamable HTTP / SSE endpoint that any MCP client can connect to.

You decide what tools that endpoint exposes by wiring regular n8n nodes into the trigger. An HTTP Request node becomes a tool. A Postgres node becomes a tool. A Slack node becomes a tool.

Each connected node shows up in the client's tools/list response, with its parameters described as a JSON schema the model can reason over.

So you are not writing protocol code. You are dragging the same nodes you already use in n8n, and the trigger handles the MCP plumbing.

n8n as an MCP Client (MCP Client Tool)

The MCP Client Tool node does the opposite. It lets an n8n AI Agent node call tools that live on an external MCP server.

Say you built an AI Agent workflow in n8n and you want it to use the GitHub MCP server. You add an MCP Client Tool node, point it at the GitHub MCP endpoint, and the agent can now call those tools.

This is how you give an n8n agent superpowers it does not natively have — databases, browsers, third-party APIs — without building each integration yourself.

For the orchestration patterns behind multi-tool agents, see multi-agent MCP with CrewAI and LangChain and how MCP tool calling works.

Step by Step: Expose an n8n Workflow as an MCP Server

Here is the shortest path from blank canvas to a working MCP endpoint.

1. Create a new workflow and add the MCP Server Trigger node.
2. Copy the MCP URL it generates — this is the endpoint clients connect to.
3. Add a tool node (e.g. HTTP Request or Postgres) and connect it to the trigger's tool output.
4. Give the tool node a clear name and description — this is what the model sees.
5. Turn on Bearer auth on the trigger and save the token somewhere safe.
6. Activate the workflow. An inactive workflow will not serve MCP requests.

That last step trips up everyone once. The MCP Server Trigger only responds when the workflow is active — a saved-but-inactive workflow returns nothing.

Connect Your n8n MCP Server to Claude

Once the endpoint is live, connecting Claude is a config edit.

For Claude Desktop, add your n8n endpoint to the MCP config file. Remote HTTP servers go under mcpServers with the URL and your bearer token:

{
  "mcpServers": {
    "n8n": {
      "url": "https://your-n8n-host/mcp/your-workflow-id/sse",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Restart Claude Desktop and your n8n tools appear in the tool list. For the full config-file walkthrough across clients, see the MCP config files guide and how to set up MCP in Claude Desktop.

Using Cursor instead? The flow is nearly identical — drop the same URL into Cursor's MCP settings (Cursor MCP setup guide).

Test Your n8n MCP Server Before You Connect It

Problem: you wire up the workflow, paste the URL into Claude, and the model either ignores your tool or calls it with the wrong arguments.

That wastes time, because you are debugging two systems at once — n8n and the client — with no visibility into either.

The fix is to test the endpoint in isolation first. Open the URL in a browser-based MCP tester, watch tools/list return your tools, and call one by hand.

If the tool names and schemas look right there, the problem is your client config. If they look wrong, the problem is your n8n wiring. You just halved the debugging surface.

Common n8n MCP Errors & Fixes

The same handful of problems account for most failed connections.

• Client connects but sees no tools: the workflow is not active, or no tool nodes are wired into the trigger.
• 401 / Unauthorized: the bearer token in your client config does not match the trigger's token.
• Model never calls the tool: vague tool names or empty descriptions — rename them so the intent is obvious.
• Tool runs but returns nothing useful: the connected node returns raw data the model cannot parse; shape the output to plain text or clean JSON.
• Works locally, fails when remote: your n8n instance is not reachable over HTTPS, or a proxy is stripping the SSE connection.

For a broader checklist, see MCP server troubleshooting.

n8n MCP vs Building a Custom MCP Server

n8n is not always the right tool. Pick based on what you are building.

Use the n8n MCP Server when…

• The logic is already a workflow — approvals, data syncs, notifications.
• You want non-developers to edit what the agent can do.
• You need a dozen integrations stitched together fast, with no SDK code.

Build a custom MCP server when…

• You need fine control over tool schemas, errors, and streaming.
• The server is a product surface, not an internal automation.
• Performance and versioning matter more than drag-and-drop speed.

If you land on the custom route, start with the Node.js MCP server guide or the Python FastMCP tutorial. You can also wrap your existing API — see wrapping APIs as MCP tools.

Already automate with Zapier? The same idea applies there — compare with Zapier MCP for Claude.

Frequently Asked Questions

Related Guides

• What Is the Model Context Protocol (MCP)?
• Zapier MCP for Claude — Automations Guide
• Wrap Existing APIs as MCP Tools
• The Complete Guide to MCP Config Files
• MCP Server Troubleshooting — Common Errors

Further Reading

• n8n Docs: MCP Server Trigger node
• n8n Docs: MCP Client Tool node
• Official: MCP Specification
• Official: MCP Transports