MCP server Official

n8n MCP Server Trigger

n8n core node that turns a workflow into an MCP server exposing n8n tools to MCP clients.

Author
n8n
Works with
Any MCP client
Documented
Oct 2, 2026

What n8n MCP Server Trigger is

The MCP Server Trigger node lets n8n act as an MCP server, making n8n tools and workflows available to MCP clients. It exposes a URL and only connects to tool nodes. It supports SSE and streamable HTTP, not stdio.

What it does

How n8n MCP Server Trigger plugs in: which agents run it and what it addsRUNS INYour agentAny MCP clientone host documentedMCP SERVER · OFFICIALn8n MCP Server TriggerConnect the agent to tools, data…5 install steps1 permission noteWHAT IT ADDSWhat it doesExposes attached tool nodes to MC…Exposes workflows via the Custom…Provides separate test and produc…Supports None, Bearer or Header a…agent → extension → new capability · from the official repository or docs
Where n8n MCP Server Trigger runs and what it adds, from its documentation
  • Exposes attached tool nodes to MCP clients via a URL
  • Exposes workflows via the Custom n8n Workflow Tool node
  • Provides separate test and production MCP URLs
  • Supports None, Bearer or Header authentication
  • Allows a custom URL path

When to use it

Good fit

  • You want Claude Desktop or another client to call your n8n tools
  • You self-host n8n and want to expose workflows as MCP tools

Not for

  • stdio transport clients without a proxy
  • Queue mode with multiple webhook replicas unless /mcp* is routed to a single replica

How to install n8n MCP Server Trigger

You need: An n8n instance

  1. Add the MCP Server Trigger node to a workflow
  2. Attach tool nodes (or Custom n8n Workflow Tool)
  3. Set authentication (Bearer or Header recommended)
  4. Publish the workflow and copy the Production URL
  5. Add the URL to the client, e.g. via npx mcp-remote for Claude Desktop
Configuration example (from the official docs)
{
  "mcpServers": {
    "n8n": {
      "command": "npx",
      "args": ["mcp-remote","<MCP_URL>","--header","Authorization: Bearer ${AUTH_TOKEN}"],
      "env": {"AUTH_TOKEN": "<MCP_BEARER_TOKEN>"}
    }
  }
}

Permissions and security

What it can access

  • Executes the tool nodes attached to it

Security notes from the maintainers

  • Authentication can be set to None; docs offer Bearer and Header auth

Review the source before granting an agent access to credentials or production systems. We document what the maintainers state; we do not audit code.

Limitations

  • No stdio transport
  • Multiple webhook replicas break SSE/streamable HTTP unless /mcp* goes to one replica

Tools it extends

Frequently asked questions

What does the n8n MCP Server Trigger node do?

It makes n8n act as an MCP server exposing tools and workflows to MCP clients. source

Which transports does the n8n MCP Server Trigger support?

SSE and streamable HTTP; stdio is not supported. source

How do I connect Claude Desktop to the n8n MCP Server Trigger?

Use npx mcp-remote with the MCP URL and a Bearer header in claude_desktop_config. source

Does the n8n MCP Server Trigger work in queue mode?

Yes with a single webhook replica; with several, route all /mcp* requests to one dedicated replica. source

Related guides

Sources and gaps

Not stated by the maintainers: license; last_release.

More extensions to look at