The MCP Client node currently fails to connect to MCP servers using self-signed certificates. Unlike the HTTP Request node which has SSL options ("Accept all certificates" or 'Ignore SSL Error' etc), the MCP Client node lacks these configuration options.
Current Issue:
- MCP Client node cannot connect to self-signed MCP servers
- No way to disable SSL verification or accept self-signed certificates
- HTTP Request node works fine with identical settings
Current Workaround:__ Using HTTP Request node with manual JSON-RPC calls, but this defeats the purpose of having a native MCP client that can automatically discover and use available tools.
What is the error message (if any)?
Error 1 => Could not connect to your MCP server
Error 2 => Connection error: self-signed certificate in certificate chain
Please share your workflow
Share the output returned by the last node
Information on your n8n setup
n8n version: 2.3.0
Database (default: SQLite): SQLite
n8n EXECUTIONS_PROCESS setting (default: own, main): main
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Please note, the entire setup and Credentials (using Header Auth) works perfectly with HTTP node with POST request. The HTTP post sample included below