Connector tool calls generating fresh MCP session each invocation

API Bugs
1

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.

3 Likes
2

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.