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
Apify MCP Server
Apify documents an official Model Context Protocol server hosted at https://mcp.apify.com that speaks Streamable HTTP in line with the current MCP specification; Apify warns that SSE transport was deprecated for removal April 1, 2026. Hosted clients authenticate through browser OAuth or by supplying Bearer tokens sourced from Console → Settings → Integrations (`APIFY_TOKEN`), can pin tool bundles via URL query (`?tools=actors,docs,apify/rag-web-browser` style examples reproduce Apify wording), optionally append `telemetry-enabled=false`, and benefit from inferred structured-output schemas surfaced for Actor tooling on hosted endpoints unlike the default stdio server. When MCP clients refuse remote transports, docs recommend `npx -y @apify/actors-mcp-server` with `APIFY_TOKEN` for stdio, Node.js ≥18, and adherence to documented per-user throughput (Apify cites up to thirty requests per second across Actor runs plus storage/documentation calls). Specialized payment modes (open x402 on Base plus Skyfire) appear as optional adjunct pages inside the broader integration handbook.
Mem0 MCP Server
Mem0 documents a hosted Model Context Protocol server at https://mcp.mem0.ai/mcp that exposes Platform memory tools (`add_memory`, `search_memories`, `get_memories`, `update_memory`, `delete_memory`, `delete_all_memories`, `delete_entities`, `list_entities`, `list_events`, `get_event_status`) to Claude, Claude Code, Codex, Cursor, Windsurf, VS Code, and OpenCode. Setup uses `npx mcp-add` with HTTP transport or manual JSON/TOML client configs; Codex requires `MEM0_API_KEY` as bearer token per docs.mem0.ai/platform/mem0-mcp. The cloud server needs a Mem0 Platform API key from the dashboard and Node.js for the installer—no local vector database required for the hosted path.
Composio MCP Server
Composio documents MCP server creation through its SDK and dashboard at docs.composio.dev: developers call `composio.mcp.create()` with toolkit names, auth config IDs, and an `allowed_tools` list, then generate per-user MCP URLs via `composio.mcp.generate(user_id, mcp_config_id)`. Hosted endpoints follow the pattern `https://backend.composio.dev/v3/mcp/{SERVER_ID}?user_id=...` and require an `x-api-key` header when `require_mcp_api_key` is enabled (default for new orgs). Docs show wiring these URLs into OpenAI Responses API, Anthropic MCP client beta, Mastra MCPClient, Claude Desktop, and Cursor. Composio notes that dynamic sessions are recommended for most use cases, while single-toolkit MCP configs suit fixed integration surfaces.