Fix MCP client HTTP transport compatibility for multiple calls #852
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.
Summary
Fixes the "Task group is not initialized" error that occurs on subsequent MCP client calls when using HTTP transport. The first call succeeds but subsequent calls fail with 500 Internal Server Error.
Related: OCPERT-275
Root Cause
The MCP data collector was using
asyncio.run()for each call, which creates a new event loop every time. FastMCP's streamable-http transport requires persistent event loop and session management - creating new loops breaks the internal task group state.This is a known issue in the MCP ecosystem:
Changes
MCP Server:
MCP Data Collector Client:
streamable_http_clientAPITesting
Verified with test script making 3 consecutive calls:
Deployment Notes
After merge, remote server needs:
pip3 install -r mcp_server/requirements.txt --upgradecurl http://localhost:8000/healthCompatibility