n8n can connect directly to the 101domain MCP Server using its built‑in MCP Client Tool node—no mcp-remote bridge required. This page shows how to configure the node to use HTTP Streamable transport, point it at https://mcp.101domain.com, and store your 101domain API key as a secure header credential in n8n’s credential vault instead of hard‑coding it in a workflow.
Configuration:
n8n (v2.16.1) has native HTTP Streamable MCP support — no mcp-remote needed. Use the MCP Client Tool node:
-
Set Transport to
HTTP Streamable -
Set Server URL to
https://mcp.101domain.com -
Under Authentication, select Header Auth and create a credential:
-
Header name:
Authorization -
Value:
Bearer your-api-key-here
-
Store the credential in n8n's credential vault — never enter the key inline in a workflow node.