feat: Add CORS configuration for browser-based MCP clients #1059
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
Mcp-Session-Id
headerProblem
Browser-based MCP clients cannot access the
Mcp-Session-Id
header from initialization responses due to CORS restrictions. Without this header, they cannot establish sessions with MCP servers.Solution
This PR adds Starlette's
CORSMiddleware
to the example servers and configures it to expose theMcp-Session-Id
header viaexpose_headers
. The configuration is minimal, only allowing the HTTP methods required by the MCP protocol (GET, POST, DELETE).Changes
CORSMiddleware
import and configuration to:examples/servers/simple-streamablehttp/mcp_simple_streamablehttp/server.py
examples/servers/simple-streamablehttp-stateless/mcp_simple_streamablehttp_stateless/server.py
Test plan
Mcp-Session-Id
header from responsesReported-by: Jerome