Lou Dalo

hey all. i'm trying to figure out the n8n mcp server trigger, and i'm in this weird situation. hoping you have some idea what's going on or how to troubleshoot: - n8n instance is self hosted community edition on hostinger, docker container - i set up an mcp server trigger in an n8n workflow - i edited the claude desktop config file to add the supergateway connection to the n8n mcp production server URL - i closed and reopened claude desktop and get a connection error message - i curl'd the supergateway connection to the mcp server manually and it works fine - used claude to troubleshoot each step and all the logs. it tells me everything's working but the claude desktop is requesting a different version of the mcp protocol than the one n8n is responding with. - does this make sense if all my installs have been upgraded to latest versions? and if so, how / where would i change the version numbers to make them compatible? I'm thinking probably supergateway would need to be upgraded ... but i don't see anything in the git repo that shows any variable where i can specify it; nor can i see any specification of the version number in n8n settings, or in the docker container yaml ringing bells for anyone? all thoughts and insights welcome!

New comment May '25

Lou Dalo

0 likes • May '25

@Jajeh Ogma I wondered if it was something with my self hosted instance so I got a free trial of n8n. It behaves the same way the initial connection happened successfully, but immediately after the connection is established somehow a termination message is sent and in the log the only thing that looks weird is that the protocol version that’s returned from N8N that instance is different. I really don’t know if that’s enough to cause the problem since the protocol supposed to be reverse compatible… But I can’t think of anything else right now That it could be. The only other thing I found in the community discussion is that the reverse proxy timeout might be an error, but that shouldn’t be a problem with the paid service, besides which I have no access to those parameters with the pay service so I assume they’re set properly I have tried other MCP servers like pinecone, and I noticed in the log that the pinecone MCP server does return the same date as the one that’s originated from Claude it’s a 2024 version that does seem to add another point to the protocol version mismatch being the cause of the error.... But I’m still confused about that because the N8N paid Service returns the 2025 protocol version So still confused…

Grayson Ho

May '25 •

💬 General discussion

Welcome to AI Builders Lab 🚀

Hey everyone! I’m Grayson, and I’m so glad you’re here. Drop a comment below to introduce yourself, and share what kind of content, tools, or support you’d love! 𝗔 𝗹𝗶𝘁𝘁𝗹𝗲 𝗮𝗯𝗼𝘂𝘁 𝗺𝗲: I started this community after spending years building products at scale, leading engineering at multiple startups, and most recently diving deep into the world of AI agents and automations. But honestly? The real magic didn’t happen until I started building in public — sharing experiments, breaking things, learning fast, and connecting with others doing the same. 𝗜 𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗔𝗜 𝗕𝘂𝗶𝗹𝗱𝗲𝗿𝘀 𝗟𝗮𝗯 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗜 𝗸𝗲𝗽𝘁 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴: “What if there was a place where we could build together, smarter, faster, without gatekeeping, and actually help each other ship cool, useful things with AI?” 𝗦𝗼 𝘁𝗵𝗮𝘁’𝘀 𝘄𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗮𝗯𝗼𝘂𝘁. We’re here to shape this together 💪 Cheers, Grayson

New comment 2d ago

Lou Dalo

2 likes • May '25

Howdy!

1-2 of 2

Level 1

2points to level up

Lou Dalo

@lou-dalo-4720

Marketing Growth and AI Solutions Advisor

Active 18h ago

Joined May 21, 2025

Contributions

Followers

Following