The MCP Server Trigger is a workflow-level entry point. You create a dedicated workflow, drop in the MCP Server Trigger node, and attach tool nodes to it. Each trigger gets its own unique URL that external AIs can call.

Unlike the Gateway, you’re building the workflow yourself. You decide exactly which tools to expose, what authentication to require (header auth or bearer), and how the workflow processes requests.

When to Use the MCP Server Trigger

  • You want full control over which tools are exposed together
  • You prefer header auth over OAuth (simpler, no token refresh)
  • You want to use the Custom n8n Workflow Tool to expose entire workflows as tools
  • You’re building a dedicated MCP endpoint for a specific AI client

Think of it as a side door with its own lock. More setup, but you control exactly who gets in and what they can reach.

⚠️ On Authentication: The MCP Server Trigger supports header auth and bearer auth. Running it with no authentication is technically possible but means anyone who finds the URL can call your tools. That’s essentially a verbose, self-describing webhook with zero protection. Always use auth.

Real-World Setup

We use the MCP Server Trigger for our AI assistant setup. Here’s what we’ve connected — each is an n8n workflow the AI can call on demand:

Related Posts

← Back to MCP Overview
MCP Access Deep Dive →
MCP Server Trigger Deep Dive →
MCP Node Deep Dive →
MCP Client Tool Deep Dive →