n8n MCP Server Trigger: Expose Any Workflow as an AI Tool

The n8n MCP Server Trigger turns a workflow into an MCP server: you attach tool nodes to it, publish, and any MCP client that connects to its URL can list those tools and call them. Adding the node takes five minutes. What decides whether an AI client calls the right tool with the right arguments is the name, description and input schema you give each tool, which is where this guide spends most of its time.

Checked October 2026 against n8n's docs for the MCP Server Trigger, the Call n8n Workflow Tool and $fromAI(), the node source in n8n 2.42.6 (the stable release on 9 October 2026), the Claude Code MCP docs, Anthropic's guide to defining tools and the MCP specification's tools page. The workflow JSON was checked against the node source and not executed, so test it on the test URL first.

This tutorial is part of our n8n hub. If MCP itself is new, read our plain-language MCP guide first; it explains servers, clients and tools.

n8n MCP server: the trigger node or the instance-level server?

n8n has two things called an MCP server, and they do different jobs. This page is about the first.

The instance-level server has its own walkthrough in connecting n8n to Claude Code via MCP. Use the trigger node when you want a client to have three or four specific abilities and nothing else.

How the MCP Server Trigger works

It is a trigger with no regular output. The docs put it this way: the node "only connects to and executes tool nodes". A client talks to it in four moves, and your design work decides the third.

Prerequisites

Set up the n8n MCP Server Trigger: the steps

Here is the finished workflow. Copy it, paste it onto a blank canvas, select your Google Calendar and Bearer Auth credentials, and replace the calendar ID in both tool nodes.

{
  "name": "Booking MCP server",
  "nodes": [
    {
      "parameters": {
        "authentication": "bearerAuth",
        "path": "booking",
        "instructions": "Tools for booking a 30 minute call. Always call check_availability for a time range before create_booking. Send times as ISO 8601 with a UTC offset. Never create an event the person has not confirmed."
      },
      "id": "e5c0a6d3-0001-4a4f-9c5e-000000000001",
      "name": "Booking MCP server",
      "type": "@n8n/n8n-nodes-langchain.mcpTrigger",
      "typeVersion": 2,
      "position": [
        0,
        0
      ],
      "webhookId": "e5c0a6d3-0004-4a4f-9c5e-000000000004"
    },
    {
      "parameters": {
        "descriptionType": "manual",
        "toolDescription": "Check whether a time range is free on the booking calendar. Use it before create_booking and whenever someone asks if a time is open. Pass start and end as ISO 8601 with a UTC offset, for example 2026-10-14T15:00:00+02:00, and keep the range to the length of one call. Returns available: true when nothing is booked in that range. It does not suggest other times.",
        "resource": "calendar",
        "operation": "availability",
        "calendar": {
          "__rl": true,
          "mode": "id",
          "value": "REPLACE_WITH_CALENDAR_ID@group.calendar.google.com"
        },
        "timeMin": "={{ $fromAI('start', 'Start of the range to check, ISO 8601 with UTC offset, for example 2026-10-14T15:00:00+02:00', 'string') }}",
        "timeMax": "={{ $fromAI('end', 'End of the range to check, ISO 8601 with UTC offset', 'string') }}",
        "options": {}
      },
      "id": "e5c0a6d3-0002-4a4f-9c5e-000000000002",
      "name": "check_availability",
      "type": "n8n-nodes-base.googleCalendarTool",
      "typeVersion": 1.3,
      "position": [
        -120,
        220
      ]
    },
    {
      "parameters": {
        "descriptionType": "manual",
        "toolDescription": "Create a calendar event for a confirmed call and invite the attendee. Only use it after check_availability returned available: true for the same start and end, and after the person has confirmed the time. Pass start and end as ISO 8601 with a UTC offset. It cannot move or cancel an existing event.",
        "resource": "event",
        "operation": "create",
        "calendar": {
          "__rl": true,
          "mode": "id",
          "value": "REPLACE_WITH_CALENDAR_ID@group.calendar.google.com"
        },
        "start": "={{ $fromAI('start', 'Start of the call, ISO 8601 with UTC offset, for example 2026-10-14T15:00:00+02:00', 'string') }}",
        "end": "={{ $fromAI('end', 'End of the call, ISO 8601 with UTC offset', 'string') }}",
        "additionalFields": {
          "summary": "={{ $fromAI('title', 'Short event title, for example Intro call with Dana Lee', 'string') }}",
          "attendees": [
            "={{ $fromAI('attendee_email', 'Email address of the person booking the call', 'string') }}"
          ],
          "sendUpdates": "all"
        }
      },
      "id": "e5c0a6d3-0003-4a4f-9c5e-000000000003",
      "name": "create_booking",
      "type": "n8n-nodes-base.googleCalendarTool",
      "typeVersion": 1.3,
      "position": [
        120,
        220
      ]
    }
  ],
  "connections": {
    "check_availability": {
      "ai_tool": [
        [
          {
            "node": "Booking MCP server",
            "type": "ai_tool",
            "index": 0
          }
        ]
      ]
    },
    "create_booking": {
      "ai_tool": [
        [
          {
            "node": "Booking MCP server",
            "type": "ai_tool",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "executionOrder": "v1"
  }
}

The calendar is fixed in both nodes, so no client can read or write any other calendar. sendUpdates is set to all, which the node describes as notifications sent to all guests.

n8n MCP URL: test, production and what the path means

The node shows both URLs at the top of its panel. They differ by one path segment and by when they listen.

The mcp and mcp-test segments are n8n's defaults (N8N_ENDPOINT_MCP and N8N_ENDPOINT_MCP_TEST in the config source). Pick a path that is hard to guess if you run without authentication, though a path is not a secret: it ends up in client configs and logs.

Expose an n8n workflow as an MCP tool the model calls correctly

A model never sees your workflow. It sees a name, a description and a schema, and chooses from those. Anthropic's tool documentation is blunt about the priority: "Provide extremely detailed descriptions. This is by far the most important factor in tool performance." It asks for what the tool does, when it should and should not be used, what each parameter means and any caveats, in at least three or four sentences. In n8n, each of those pieces comes from a specific setting:

Two smaller rules. Keep the tool list short: n8n's own docs note that a built-in tool gives "tighter control" because you fix the operation and pin parameters, and every extra tool is one more thing to choose wrongly. And return little: a tool that answers available: true is easier for a model to act on than one that returns a raw API response.

When one node is not enough: Call n8n Workflow Tool

To expose a whole workflow as one tool, attach a Call n8n Workflow Tool node instead of an app tool. Three settings matter:

1. The sub-workflow's inputs. Start it with the When Executed by Another Workflow trigger and set Input data mode to Define using fields below. Those fields become the tool's inputs.
2. Description. The same rules as above. This text is the only thing a client knows about the workflow.
3. Workflow Inputs. For each field, either fix a value or let the model supply it with $fromAI().

The sub-workflow has to be published. If it is not, the docs say the call fails with Workflow is not active and cannot be executed, returned as the tool result, which is easy to miss inside a longer answer. A good use: one book_call tool whose sub-workflow checks availability, creates the event and sends a confirmation, so the model makes one decision and not three.

Connect a client

Claude Code connects to the production URL directly. The header flag carries the token from your Bearer Auth credential:

claude mcp add --transport http booking https://n8n.example.com/mcp/booking \
  --header "Authorization: Bearer <your-token>"

Run /mcp inside Claude Code to confirm the server is connected and lists two tools. For Claude Desktop, the n8n docs use the mcp-remote gateway in the app's config file, with the same URL and header. Other servers worth running next to it are in our list of the best MCP servers for coding.

Authentication: who can call your tools

Whoever can connect can run your tools with the credentials saved in n8n. The node offers four settings in 2.42.6; the docs list the first three.

Authentication decides who gets in, not what they can do. That part is the tool design: a tool that can only create an event on one calendar cannot be talked into deleting anything. The MCP specification adds that a human should be able to deny tool calls, so prefer clients that ask before running a write tool.

Troubleshooting

In queue mode there are two more limits worth knowing: a queued tool call gets 120 seconds by default in 2.42.6, and a tool result larger than the webhook relay limit comes back as a tool error. Our n8n queue mode guide covers both settings.

Tool design is a skill that outlasts any one platform. Our AI SaaS Builder program has no n8n lessons, but it spends two modules on MCP in code: building your first MCP server, MCP use cases for a SaaS and building MCP into your own product.

n8n MCP Server Trigger: FAQ