# Connector tool calls generating fresh MCP session each invocation **URL:** \ **Category:** Bugs\ **Tags:** connector\ **Created:** [November 3, 2025, 11:47pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975 "2025-11-03T23:47:03Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [November 3, 2025, 11:47pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/1 "2025-11-03T23:47:03Z")
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. ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [November 4, 2025, 2:01am UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/2 "2025-11-04T02:01:05Z")
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. ---
**Author:** ![dannyyy.jimenez](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@dannyyy.jimenez](https://community.openai.com/u/dannyyy.jimenez)\ **Post date:** [November 20, 2025, 1:36am UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/3 "2025-11-20T01:36:42Z")
Seeing this being an issue again, after each tool call ChatGPT ui is sending a new session id in the request params ---
**Author:** ![dannyyy.jimenez](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@dannyyy.jimenez](https://community.openai.com/u/dannyyy.jimenez)\ **Post date:** [December 1, 2025, 2:20pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/4 "2025-12-01T14:20:05Z")
Bumping this to see if anyone is experiencing the same behavior or has a solution for this? ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [December 24, 2025, 12:29am UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/5 "2025-12-24T00:29:00Z")
+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. ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [December 24, 2025, 9:51pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/6 "2025-12-24T21:51:15Z")
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. ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [December 29, 2025, 4:58pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/7 "2025-12-29T16:58:39Z")
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. ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [December 29, 2025, 11:17pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/8 "2025-12-29T23:17:24Z")
@OpenAI_Support how do we get someone engaged here? ---
**Author:** ![dannyyy.jimenez](https://avatars.discourse-cdn.com/v4/letter/d/e9c0ed/32.png) [@dannyyy.jimenez](https://community.openai.com/u/dannyyy.jimenez)\ **Post date:** [December 30, 2025, 8:35pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/9 "2025-12-30T20:35:29Z")
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 ---
**Author:** ![HungryHippo5](https://avatars.discourse-cdn.com/v4/letter/h/9de0a6/32.png) [@HungryHippo5](https://community.openai.com/u/HungryHippo5)\ **Post date:** [December 30, 2025, 9:15pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/10 "2025-12-30T21:15:45Z")
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. ---
**Author:** ![Alokai](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@Alokai](https://community.openai.com/u/Alokai)\ **Post date:** [January 15, 2026, 1:26pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/11 "2026-01-15T13:26:55Z")
Today I started my MCP server (ChatGPT App) which wasn’t used for over a month. Despite no code changes in the MCP server itself, I noticed the exact same problem as the OP. Every request produces a completely new “mcp-session-id” header… ---
**Author:** ![Roman\_Barashkov](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/roman_barashkov/32/717945_2.png) [@Roman\_Barashkov](https://community.openai.com/u/Roman_Barashkov)\ **Post date:** [January 23, 2026, 6:18pm UTC](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975/12 "2026-01-23T18:18:14Z")
Hi there! I had the same issue and spent a lot of time with mcp documentation. But found this example: That repository with examples helps me at **github** → **openai/openai-apps-sdk-examples/tree/main/shopping\_cart\_python** So, as I correctly understand, we should pass `_meta["widgetSessionId"]`In each response, apply that `session_id` to each input tool. Also, I generate a new `session_id` in each tool when the input `session_id` is empty. That helps me initialize my session on each new chat window for any tool call. Also duplicate that `session_id` in `structuredContent` for model context. Additionaly I add guide into MCP-server `instructions` `SESSION ID (CRITICAL)` `When ANY tool returns a session_id in its response (structuredContent), you MUST pass that same session_id to ALL subsequent tool calls within the same conversation. This ensures consistent data and state throughout the user's session.` `Tools that use session_id: tool_1, tool_2, tool_n.` Hope you also resolving that issue in your projects 🙏