Connector tool calls generating fresh MCP session each invocation

I am currently testing a new MCP connector in Developer Mode. As part of my implementation, I am tying session state to the Mcp-Session-Id generated.

Last week, things were working as expected - when I made a series of tool calls, the same session ID was being reused across, so behavior was working.

It looks like something has changed within the past 72 hours - each tool invocation is now triggering a fresh Initialize JSON-RPC message to my MCP server without the prior Mcp-Session-Id header, so each tool call is now triggering a different session.

Did something change here? Please investigate and confirm expected behavior.

4 Likes

Seems to be working as of now… would nonetheless be good to get confirmation of the behavior, and whether this was a regression or if this is an intentional change.

Seeing this being an issue again, after each tool call ChatGPT ui is sending a new session id in the request params

1 Like

Bumping this to see if anyone is experiencing the same behavior or has a solution for this?

+1 - I’m also experiencing the same. This is really crucial - what I’m looking at is dependent upon the generated session ID being maintained properly.

Can we get an ack on this from OpenAI folks? I’ve not been able to see any definitive description of what the expected behavior is, so it makes building any feature based around this really shaky if we cannot guarantee this.

1 Like

I reported a bug via the ChatGPT app and had someone from the support team reach out via email. I’ve responded with some network traces and a screen capture to show the behavior.

Fingers crossed this gets forwarded onto the engineering team and we get a meaningful resolution here. Will share any updates I get.

1 Like

Just following up - I was able to get a customer support email thread going. HOWEVER…that process has been nothing but a headache.

tl;dr - you are required to upload a video capture directly as an attachment on the email. I had a capture, but my email provider doesn’t allow direct attachments over a certain size, so I included a link for someone to download. Instead, I got the repeated automated email saying it needs to be an attachment.

Asked to speak to a supervisor and got a new agent/AI with a different name, but largely asking for the same thing. So who knows if this will actually go anywhere.

To anyone from OpenAI that reads this - I really hope you feel embarrassed by how truly awful your collective customer support experience is.

1 Like

@OpenAI_Support how do we get someone engaged here?

interestingly enough, it seems the already deployed apps have no sort of state management outside of the widget. Most “Brand Names” seem to reroute you to their website / app as soon as you ask for a request to continue the session there

1 Like

I’ve noticed this too - everything so far seems to be experiences that don’t really require long-term session management with the MCP server. Maybe this is a known limitation internally that they are just not being forthcoming about.

That said, it’s impossible to say because there is still no acknowledgement on any of this! I was able to fire off a response to customer support email and captured a short enough zipped screen capture that could be directly attached to email, but not heard back yet. Will keep this thread posted if I learn anything.

1 Like