Http:// insted of https://

Questions
1

Describe the problem/error/question

I’m going to connect n8n to claude desktop. in connectors menue, asks the server address and says that must start with https:// but when I refer to n8n mcp pat and see the address is began with http://. what can i DO?

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

2
21041×902 22.9 KB

1
1586×451 28 KB

Information on your n8n setup

  • n8n version: 2.43.8
  • Database (default: SQLite):SQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):docker
  • Operating system: win 11 pro
2

Hey @Seyyed_Reza_Mirabed, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@kjooleng, @GeoffS, @krisn0x - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Hey @Seyyed_Reza_Mirabed welcome to the n8n community.
Your screenshot shows localhost, which only works on your own PC. Claude’s remote connectors connect from Anthropic’s servers, even in Claude Desktop, so this connection needs a public HTTPS address.

For a quick setup, install and authenticate ngrok on Windows, then run ngrok http 5678. Add N8N_EDITOR_BASE_URL=https://YOUR-NGROK-HOST and N8N_PROXY_HOPS=1 to your existing n8n container’s environment and recreate the container with its existing data volume. Open n8n through that HTTPS address, then enter https://YOUR-NGROK-HOST/mcp-server/http in Claude and approve the OAuth connection. Keep ngrok running while using it.

4

That http:// is probably just what n8n builds from its own settings, so it needs two things. First, Claude Desktop can only reach an https address that is publicly reachable, and a Docker container on your Windows PC is not that by default. Put a reverse proxy or a tunnel (Caddy, nginx, Cloudflare Tunnel) in front of n8n so you get a real https URL. Second, tell n8n about it by setting WEBHOOK_URL=https://your-domain/ in the container environment (and N8N_PROXY_HOPS=1 if it sits behind a proxy). Recreate the container, then reopen the MCP settings and the address should now start with https://. If it still shows http, check that the variable actually reached the container with docker exec env.