MCP server - access to request/session scope beans

Expected Behavior

My app is storing user context in request and/or session scoped beans. I'd like to access these beans from the code serving as tool in the MCP server.

Current Behavior

I'm using MCP server implementation based on Server Sent Events (WebMvcSseServerTransportProvider). The issue is that my tool code is being called from Reactor thread:

session.handle(message).block();

Because of that, my code can't access session and request scoped beans:

Error creating bean with name 'scopedTarget.requestUserDataHolder': Scope 'request' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton

I could pass this information to Reactor's context, but I don't have the access to Reactor's pipeline.

Context

It prevents me from exposing my synchronous WebMVC API using MCP.

Start with WebMvcSseServerTransportProvider and trace the session.handle(message).block() call into the tool execution path. Reproduce the request/session-scoped bean failure, then verify that tool code serving an SSE request can access the relevant scopes without breaking existing MCP handling.