fix: Set the Server session initialization state immediately after respond… #1478
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Set the Server session initialization state immediately after responding to InitializeRequest to fix the race condition that gives the following warnings
Motivation and Context
For Stateful http mcp servers (when stateless_http=False) this change is required for most clients to work correctly. I have tested this with Claude desktop and VSC. Mcp Inspector does not show the issue as it does not automatically call tools/list after initialize.
This change brings the behaviour of the mcp python-sdk inline with the TS sdk
[TS SDK link] https://github.com/modelcontextprotocol/typescript-sdk/blob/caa25503cdfc449d116c204e866bccc2617d7037/src/server/streamableHttp.ts#L501
How Has This Been Tested?
A test case is attached to the PR
main.py
uv run pytest :
Results (19.93s):
633 passed
2 skipped
1 xfailed
Breaking Changes
No
Types of changes
Checklist
Additional context