In case this is still relevant - the issue is that you MUST use a reverse-proxy in order to install an MCP server on n8n. The gist is that the reverse proxy provides a single SSL termination point that both external and internal clients can reach using the same domain name and certificate. The reason is that SSL termination is required and enforced has to do with the configuration of the MCP Server Trigger node NPM library, from what I could gather.
I’ve written an article on Medium on how to make it work with a complete setup using docker compose.