MCP Trigger Extended Header Context icon

MCP Trigger Extended Header Context

Expose n8n tools as an MCP Server endpoint

MCP Trigger Extended Header Context

AI-generated

Summary

Exposes connected n8n tools as an MCP (Model Context Protocol) server endpoint via a webhook, forwarding incoming requests to connected tools and returning results.

Inputs

  • authentication — Authentication method for inbound webhook requests (none, bearer, or header). Defaults to none.
  • path (required) — The base URL path for the MCP server endpoint. Defaults to the webhook ID.
  • exposeMcpHeaderParameters — Whether to include x-mcp-* parameters in the MCP tool schemas returned to clients.
  • optionalParameters — Comma- or newline-separated parameter names to treat as optional when exposing and validating tool calls.

Output shape

A single JSON object containing execution metadata (e.g., mcpToolCall, mcpMessageId, mcpListToolsRelay) when a tool call or list tools request is received.

Returns an empty object for non-tool requests (e.g., setup, DELETE). The node connects to upstream tools via the 'Tools' input connection.

Examples

Example 1: Receiving a tool call

Configure authentication to 'none' (or required auth), set a path, and connect an AI tool node upstream.

Example 2: Receiving a list tools request

Set path and expose optional parameters if needed. The node returns a relay marker for list tools requests.

Links

Discussion