The MCP Server Trigger is a first-party n8n core node that turns an n8n workflow into a Model Context Protocol server endpoint. Instead of chaining conventional trigger nodes, it connects only to tool nodes so remote MCP clients can list tools and invoke them over long-lived Server-Sent Events or streamable HTTP transports (stdio is explicitly unsupported). Each node exposes separate test and production MCP URLs, optional bearer or header authentication, and documentation explains how to proxy Claude Desktop through `npx mcp-remote` plus queue-mode caveats for multi-replica webhook deployments.
Use cases
- Exposing calendar, CRM, or ticketing tool nodes to Claude Desktop via MCP without writing a separate microservice
- Packaging approved sub-workflows as callable tools through the Custom n8n Workflow Tool node
- Prototyping authenticated MCP surfaces with rotating test URLs before publishing production endpoints
- Pairing n8n’s MCP Client Tool node with MCP Server Trigger for bidirectional agent automation
- Operating single-replica webhook pools or dedicated `/mcp*` ingress routes to keep SSE sessions sticky
Key features
- Claude Desktop
- Cursor
- Codex
Frequently Asked Questions
- Does it support stdio transports?
- No. n8n’s documentation states only SSE and streamable HTTP are supported; stdio is not available for this node.
- How do I connect Claude Desktop?
- n8n documents running `npx mcp-remote <MCP_URL>` with `Authorization: Bearer` headers in `claude_desktop_config.json`, substituting the URL and token from the node.
- What breaks in queue mode with several webhook replicas?
- Docs warn that SSE/streamable HTTP require sticky routing; you must send all `/mcp*` traffic to one dedicated webhook replica or connections will drop.
Related
Related
3 Indexed items
Webflow MCP Server
Connect any LLM to your Webflow sites via the Model Context Protocol. Manage pages, collections, CMS items, e-commerce products, forms, and users through natural language — enabling AI-driven site management and content workflows.
DuckDB MCP community extension (`duckdb_mcp`)
The DuckDB-distributed community extension `duckdb_mcp` embeds MCP client and server capabilities directly inside DuckDB. Installers load it via `INSTALL duckdb_mcp FROM community` followed by `LOAD duckdb_mcp`, after which SQL can attach remote MCP servers (stdio/TCP/WebSocket transports), enumerate resources (`mcp_list_resources`), invoke remote tools (`mcp_call_tool`), and wrap responses with `read_csv`/`read_json`/`read_parquet` URIs routed through `mcp://`. In reverse direction, DuckDB can publish tables, queries, and execution-bound tools (`mcp_publish_table`, `mcp_publish_query`, `mcp_publish_execution_tool`) while `mcp_server_start` exposes them to external MCP-compatible clients.
Ollama MCP Server
Community-maintained Model Context Protocol bridge that exposes Ollama's local HTTP API—model listing, pulls, chat, and OpenAI-compatible completions—to MCP clients such as Claude Desktop and Cursor. Published on npm as `ollama-mcp-server` (maintained fork of NightTrek/Ollama-mcp); requires a running Ollama daemon reachable at `OLLAMA_HOST` (default `http://127.0.0.1:11434`).