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
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
Add the MCP Server Trigger node to a workflow
Attach tool nodes (or Custom n8n Workflow Tool)
Set authentication (Bearer or Header recommended)
Publish the workflow and copy the Production URL
Add the URL to the client, e.g. via npx mcp-remote for Claude Desktop