# Use the n8n MCP server

> Connect Claude to your n8n instance through MCP so it can find, run and build workflows, and learn the MCP Server Trigger and MCP Client Tool nodes.

Source: https://viralistic.nl/help/n8n/n8n-mcp

MCP (Model Context Protocol) is the standard way for AI assistants like Claude to use outside tools. n8n speaks MCP in three different ways, and they are easy to mix up. This article explains all three and walks you through the one most people want first: letting Claude work directly with your n8n instance.

## Three ways n8n and MCP meet

| Feature                   | Direction                   | Use it to                                               |
| ------------------------- | --------------------------- | ------------------------------------------------------- |
| Instance-level MCP server | Claude uses your n8n        | Let Claude search, run, test and build workflows        |
| MCP Server Trigger node   | Claude uses one workflow    | Offer a hand-picked set of tools from a single workflow |
| MCP Client Tool node      | n8n uses another MCP server | Give an n8n AI Agent tools from an external service     |

## The instance-level MCP server

This is built into n8n, on Cloud and self-hosted. Once you connect Claude, it can:

- Search your workflows and read the ones you expose.
- Run exposed workflows and check their executions.
- Test workflows with sample (pinned) data.
- Create and edit workflows and data tables, and publish workflows.

> **Note:** Building and editing workflows over MCP needs a recent n8n version (2.13 or later, according to the n8n docs). Older instances can only search and run workflows. Menu names below match current versions and may differ slightly on older ones.

### Turn it on

1. In n8n, open **Settings** and go to **Instance-level MCP**. You need to be the instance owner or an admin.
2. Select **Enable MCP access**.
3. In **Connection details**, select **Connect**. A dialog shows the **Server URL**, which ends in `/mcp-server/http`.

The dialog offers two ways to authenticate: **OAuth** (recommended, you approve each client in n8n) or an **API key** (a personal access token sent as a bearer header). n8n shows the token only once, so copy it straight into your client.

### Connect Claude (desktop app or claude.ai)

1. In the n8n **Connect** dialog, choose your client. For claude.ai there is a one-click setup.
2. Or add it yourself: in Claude, open **Settings**, then **Connectors**, and add a custom connector.
3. Paste the **Server URL**. This is not the address of your n8n editor, so do not copy it from the browser bar.
4. Save, then approve the access request that n8n shows you.

See [Connect Claude to your tools](https://viralistic.nl/help/claude/connectors) for more on connectors.

### Connect Claude Code

Run this in your terminal, with your own domain:

```bash
claude mcp add --transport http n8n https://your-n8n-domain/mcp-server/http
```

Then run `/mcp` inside Claude Code, select **n8n** and complete the sign-in. To use an API key instead, add `--header "Authorization: Bearer YOUR_TOKEN"` to the command.

### Choose which workflows Claude can use

Claude can see short previews of every workflow you have access to, but it can only open, run or change workflows you expose. To expose one:

1. Open the workflow, open the workflow menu (the three dots) and choose **Settings**.
2. Turn on **Available in MCP**.

You can also do this from the workflow list, or in bulk from the Instance-level MCP settings page. Add a clear description to each exposed workflow so Claude knows when to use it. To be exposed, a workflow must be published and start with a webhook, form, schedule or chat trigger. Workflows that Claude creates over MCP are exposed automatically.

> **Warning:** Every client you connect sees every workflow you exposed. You cannot limit a workflow to one client. Expose only what you are comfortable letting an AI run, and revoke clients you no longer use under **Connected clients**.

If you self-host, Claude.ai and the Claude apps need to reach your instance over the internet with HTTPS. A local `localhost` install only works with Claude Code on the same machine.

## MCP Server Trigger node

Use this node when you want to offer a small, controlled set of tools rather than your whole instance. You add the MCP Server Trigger to a workflow and attach tool nodes to it, for example a **Call n8n Workflow Tool** that runs a sub-workflow to look up a customer. The node gets its own MCP URL (test and production), with optional bearer or header authentication. Publish the workflow, then add the production URL to Claude as a connector.

## MCP Client Tool node

This works the other way round. Attach an **MCP Client Tool** to an n8n **AI Agent** node and the agent can use the tools of any external MCP server, such as your CRM or a documentation server. Enter the server endpoint, choose an authentication method, and under **Tools to Include** pick All, Selected or All Except. Exposing only the tools the agent needs keeps it focused and safer. For a fixed, non-AI step, the regular **MCP Client** node calls one chosen tool.

## A community alternative

The open source project [n8n-mcp](https://github.com/czlonkowski/n8n-mcp) by Romuald Czlonkowski gives Claude detailed documentation for n8n's nodes, plus optional workflow management through the n8n API. It is maintained independently of n8n. For most teams, the official instance-level server is the simpler and better supported choice.

## Next steps

- [Build workflows with Claude](https://viralistic.nl/help/n8n/build-workflows-with-claude)
- [The AI Agent node explained](https://viralistic.nl/help/n8n/ai-agent-node)
- [Connect Claude to your tools](https://viralistic.nl/help/claude/connectors)
- [Install Claude Code](https://viralistic.nl/help/claude/install-claude-code)