n8n MCP Server Trigger with Claude: Complete Setup Guide

n8n MCP Server Trigger with Claude: Complete Setup Guide

What Is the n8n MCP Server Trigger?

The **n8n MCP Server Trigger** is a LangChain node that turns n8n into a Model Context Protocol (MCP) server. Once configured, AI clients like Claude Desktop can list your n8n tools and call them directly from conversation. The trigger exposes a URL that Claude connects to, enabling natural-language control of your automations without switching between apps.

Unlike the instance-level MCP access (which exposes an entire n8n instance), the MCP Server Trigger node lets you craft a specific MCP server behavior inside a single workflow. Only the tools you explicitly attach to the trigger are visible to Claude. This keeps things lean and controlled.

**Use it when you want Claude to:**

- Trigger a specific n8n workflow on demand

- Call a particular workflow as a tool during a Claude conversation

- Expose only selected automation tools to an AI client, without exposing the full instance

If you want broader access across all your workflows, use instance-level MCP instead. But for targeted, purpose-built integrations, the MCP Server Trigger is the right tool.

Prerequisites

Before you start, make sure you have:

- **n8n v1.90 or later** (MCP Server Trigger is a built-in node, no separate install needed)

- **Claude Desktop** installed (download here)

- **Node.js 18+** on your machine (required for the `mcp-remote` proxy)

- A published or test workflow with at least one tool attached

Step 1: Add the MCP Server Trigger Node in n8n

Open your workflow in n8n. Add the **MCP Server Trigger** node from the LangChain section.

The node has three key settings:

MCP URL

The node shows two URLs: **Test** and **Production**.

- **Test URL**: Active when the workflow is not yet published. Calling it shows data in the workflow editor. Use this while building.

- **Production URL**: Active once the workflow is published. Calling it executes the workflow silently. Use this for real use.

Toggle between them using the dropdown at the top of the node panel.

Authentication

You can require clients to authenticate. Choose one of:

- **Bearer auth**: Send the token as an `Authorization: Bearer <token>` header

- **Header auth**: Use a custom header name and value

Set up credentials in n8n under **Settings > Credentials**, then reference them in the node.

Path

The node auto-generates a random URL path by default. You can override this with a custom path. Useful if you need consistent URLs across deployments.

Once configured, activate the workflow. n8n registers the MCP URL and it becomes callable.

Step 2: Attach a Tool to the Trigger

The MCP Server Trigger does not do anything on its own. It must connect to at least one **tool node**. The tool defines what Claude can actually call.

The most common option is the **Custom n8n Workflow Tool** node. Attach it to the MCP Server Trigger and configure which workflow it should expose:

1. Add the **Custom n8n Workflow Tool** node after the MCP Server Trigger

2. Point it to the workflow you want Claude to run

3. Give the tool a clear name and description (Claude uses this to decide when to call it)

4. Save and activate the workflow

You can attach multiple tool nodes to expose multiple workflows through a single MCP server.

Step 3: Get Your MCP URL and Bearer Token

After activating the workflow, open the MCP Server Trigger node panel. You'll see:

- **MCP URL** (Test or Production, depending on which is active)

- **Bearer Token** (visible when Bearer auth is enabled)

Copy both. You will need them for the Claude Desktop configuration in the next step.

If you are using self-hosted n8n, make sure the MCP URL is accessible from your machine. For n8n Cloud, the URL is public by default.

Step 4: Configure Claude Desktop

Open your Claude Desktop configuration file:

- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`

- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`

Add the n8n MCP server under the `mcpServers` key:

```json

{

"mcpServers": {

"n8n": {

"command": "npx",

"args": [

"mcp-remote",

"<MCP_URL>",

"--header",

"Authorization: Bearer ${AUTH_TOKEN}"

],

"env": {

"AUTH_TOKEN": "<MCP_BEARER_TOKEN>"

}

}

}

}

```

Replace `<MCP_URL>` with the URL from your MCP Server Trigger node (test or production). Replace `<MCP_BEARER_TOKEN>` with the token shown in the node.

Save the file and restart Claude Desktop.

Step 5: Verify the Connection

After restarting Claude Desktop, open a new conversation. Ask Claude:

> What n8n tools do you have access to?

Claude should respond with the name and description of the tool you attached in Step 2. If it lists your workflow tool, the connection is working.

If Claude does not list any tools:

- Make sure the workflow is activated (not just saved as a draft)

- Double-check the MCP URL is correct (use Production URL if the workflow is published)

- Confirm the Bearer token matches exactly what n8n shows

- Restart Claude Desktop completely after updating the config file

- For self-hosted n8n, verify the MCP URL is reachable from your machine (not blocked by firewall or VPN)

Step 6: Call Your n8n Workflow from Claude

Once connected, you can call the workflow directly from chat. Example prompts:

- "Run the company enrichment workflow for example.com"

- "Use the n8n workflow to send a Slack message to #alerts"

- "Check if the lead scoring workflow ran successfully for contact@example.com"

Claude sends the request to your n8n MCP Server Trigger, which executes the workflow and returns the result back through the MCP connection.

Common Mistakes and How to Avoid Them

**Workflow not activating**: The MCP Server Trigger only registers the MCP URL when the workflow is in active or test mode. A draft workflow will not respond to MCP calls.

**Wrong auth header format**: The Claude Desktop config must use the exact format `Authorization: Bearer ${AUTH_TOKEN}` (with the `${}` syntax for env variable interpolation). Do not hardcode the token value in the header line.

**Using Test URL in production**: The Test URL only works when the workflow is not published. For Claude to call the workflow reliably, use the Production URL and publish the workflow first.

**Queue mode with multiple webhook replicas**: If you run n8n in queue mode with more than one webhook replica, MCP connections may fail because SSE requires the same server instance. Route all `/mcp*` requests to a single dedicated webhook replica to fix this.

**Token not showing in node panel**: The Bearer token only displays when authentication is enabled on the MCP Server Trigger node. Enable Bearer auth and save the credentials first.

How Synta Makes This Faster

Setting up the MCP Server Trigger manually works, but building the underlying workflows still takes time. Synta is an AI-powered n8n workflow builder that generates production-ready workflows from plain English descriptions.

Instead of building the enrichment workflow, Slack notification workflow, or CRM sync workflow by hand, you can describe what you want and get a working n8n workflow in seconds. Attach it to the MCP Server Trigger, expose it to Claude, and you have a natural-language interface to your automation stack.

For example: describe "A workflow that looks up a company domain, enriches it with OpenAI data, and posts the result to Slack" and Synta generates the full n8n workflow. Then hook it up to Claude via the MCP Server Trigger.

Get started at synta.io.

FAQ

What is the difference between the MCP Server Trigger and instance-level MCP access?

Instance-level MCP access creates one connection per n8n instance and exposes all workflows you enable. The MCP Server Trigger lives inside a specific workflow and only exposes that workflow's tools. Use the trigger for targeted, scoped integrations. Use instance-level access when you want broad, centralized MCP exposure.

Can I connect other MCP clients besides Claude?

Yes. Any MCP-compatible client can connect to the MCP Server Trigger URL, including Cursor, Windsurf, and ChatGPT (where MCP is supported). The configuration steps are similar, though the config file location and format vary by client.

Does the MCP Server Trigger work with n8n Cloud?

Yes. For n8n Cloud, the MCP URL is publicly accessible by default and no additional proxy setup is required. For self-hosted n8n behind a firewall or VPN, you may need to expose the endpoint manually or use a tunnel.

How do I secure the MCP connection?

Enable Bearer auth or Header auth on the MCP Server Trigger node. Use a long, random token and never commit tokens to version control. For production use, consider restricting the MCP URL to specific IP ranges if your n8n deployment supports it.

What happens if the workflow fails?

If the workflow returns an error, the MCP Server Trigger returns an error response to Claude. You can add error handling in the workflow itself (e.g., retry logic, notification on failure) to make the experience more robust for Claude users.

Summary

The n8n MCP Server Trigger gives you a direct, programmatic connection between Claude and your n8n workflows. Add the node, attach your tools, configure Claude Desktop, and you have natural-language control of your automations.

The critical steps are: activate the workflow, get the MCP URL and Bearer token from the node, configure Claude Desktop with the correct `mcp-remote` command, and verify with a tools listing. Most setup failures trace back to the workflow not being activated or an incorrect auth token.

For a faster path to building the workflows behind the trigger, use Synta to generate them from descriptions and connect the results to Claude via MCP.

**Internal link notes:**

- [MCP docs / installation] → https://mcp-docs.synta.io/installation when talking about setting up MCP auth

- [Synta self-healing] → https://mcp-docs.synta.io/introduction when talking about Synta MCP features

- [n8n docs] → https://docs.n8n.io when referencing n8n docs for the trigger node

- [Synta website] → https://synta.io in CTA section