Hi,
I’m trying to connect a custom MCP server (implemented in Node.js/Express with @modelcontextprotocol/sdk/server/streamableHttp.js) to ChatGPT as a connector. The MCP endpoint is mounted at /sse, and I’ve set the connector URL explicitly to https://test.gurum.cat/sse.
Environment
-
MCP server: Node.js + Express +
@modelcontextprotocol/sdk/server/streamableHttp.js -
Endpoint:
https://test.gurum.cat/sse -
Connector config: no authentication
Problem
-
When I attempt to connect the server, the connector always shows “Connection failed.”
-
Looking at the server logs, I never receive a
POST /sse initializerequest. Instead, I only see repeatedGET /requests (andGET /favicon.*).[HTTP] -> GET / [HTTP] <- GET / 200 [HTTP] -> GET / [HTTP] <- GET / 200 -
The
/sseendpoint itself works fine. When I manually send aPOST /ssewith aninitializerequest viacurl, the session is created successfully andtools/listworks as expected. -
In the mcp inspector, both fetch and search methods were found to work normally.
-
However, since the connector never actually calls
/sse, the MCP initialization never starts, no session is created, and the connector UI just fails.
My questions
-
Is it expected that the connector only performs
GET /checks and never attempts to call the actual MCP endpoint (/sse)? -
Could the connector be failing at the health-check step and not proceeding to initialization at all?
-
Given that my MCP implementation at
/sseworks with manual requests, what could cause ChatGPT’s connector backend to never hit/ssein the first place?
Any guidance or examples of a working MCP server setup would be greatly appreciated.