I am hosting n8n locally, on windows. Installed mcp community node. My MCP server trigger runs fine on: http://localhost:5678/mcp-test/test/sse. The server is working fine, browser gives a response, as well as when testing it is listening, but the mcp tool itself says failed to connect.
Can someone help who solved it? I read on the internet it is common, but mostly people host somewhere else etc. Would appreciate any help.
Hello @Kacper_Kondraciuk
Feel free to check this video out on the link, Securely Self-Hosting n8n with Docker & Cloudflare Tunnel (The... Arguably Less-Painful Way) - #8 by King_Samuel_David
You could setup domain name, and https, which might solve this.
So to confirm also, your running n8n in dockers? on windows?
Where is your mcp trigger running inside n8n workflow?
Am trying to workout, as you mentioned in browser localhost works, so if n8n is in dockers that might be ure issue wrong hostname.
But id recommend to get a domain on it, your need it for certain apps because of callback URL etc.
Let me know am sure someone well answer 
Thanks I managed to fix and read a lot on it online. It was the address I had to change localhost to 127.0.0.1 and only the production sse address works, the test one is not on n8n. But it worked eventually.
Hi Kacper. Did you find a solution? I am having a similar issue but when I use MCP Inspector everything works as expected. Here are the details of my case: MCP Inspector can connect and get data but N8N MCP client not
