Bugs on n8n.io/support And problem with connecting MCP server, the "open claude" never works

Questions
1

Hi there

First of all - None of the buttons in Safari works on n8n support , had to use another browser to find the community…

And now to my real problem. I have a private instance of n8n running, everything works, except the Claude Code MCP when using the UI . Using Claude Code CLI and manually set MCP server works fine.

But when using the UI, the last step, where it actually opens Claude Code and verifies the connection, it never happens. After I click “open desktop app” nothing happens, it just stays there forever, never allowing the connection.

And in Claude Code it says

"**
Connection issue**

Couldn’t connect to the server. This is a problem on the provider’s side — contact the connector provider."

2

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

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@DariRuProg, @Gallo_AIA, @Zohar - 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

Hi @Lulzkiller666 Welcome!
Claude Code CLI connects from your own machine, while the connector flow you get from the UI is brokered server to server from Anthropic’s backend, so that path only works if the instance is reachable from the public internet. A private hostname, an RFC 1918 or internal address, a port other than 443, or a certificate served without its intermediates all fail at that hop and surface as “This is a problem on the provider’s side”, which is exactly why the same instance added manually in the CLI works.
For the connector path, serve n8n on a public hostname on 443 with the full certificate chain, allow inbound from Anthropic’s egress range 160.79.104.0/21, and check that no bot or WAF rule blocks the Claude-User agent on /.well-known/* and /mcp-server/*. A connector is immutable once created, so remove and re-add it after any URL change.
If the instance is meant to stay private, stay on the CLI setup that already works, that is the intended route for a non-public instance.
The Safari buttons on n8n support are n8n’s own site, send that one to help@n8n.io with your Safari version.
Where to Get n8n Help: Forum, Discord, GitHub & Support Channels - n8n Guide

5

Thanks for letting us know about this, We have created ADO-5762 as the internal dev ticket to look into it.