Worked well for weeks, then.... "Could not connect to your MCP server"

Questions
21

Hi @cutecatcode , sorry for my late answer.

I believe that gzip conversion is disable by default on Hostinger (I don’t found anything online to disable, only to enable).

But I don’t think it comes from Hostinger because I’ve just created a new workflow with AI Agent + MCP client + MCP Server trigger… and it works ! So I guess that if this new workflow works, thus the issues shouldn’t comes from the host.

If you’re asking, I still have the issue on the workflow I’m trying to debug haha

22

Hi @RomainMaltrud , did you find a way to resolve this problem? I’m in the same boat as you

23

Try to connect to mcp via mcp inspector MCP Inspector - Model Context Protocol

if you open the chrome dev console, have some errors inside th console ?

24

Hi @Guilherme_Gouveia , not yet… I’m still stuck with this issue. Even more strange, I’ve build other AI Agent in the meantime that works like a charm.

By the way, thanks for relaunching this topic. I’m sorry for you but at the same time I’m glad that i’m not alone

25

Hey @mredodos, thanks for your help ! I didn’t know about the MCP Inspector tool ! That looks great ! I’ll have a look and let you know how it goes

1 Like
26

Still no answers ? I have the same proble,… It never worked.. I started yesterday building this mcp server and I have the same issue

27

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.