How can I handle headers?

[thomaspeng90s]

I pass an authorization token through the header. How can I handle it, transform it into user info, and use it in my tool functions

[krzysztof-osiecki]

Same question here. I'm using my own servlet so i can handle them in it, however dont see a nice way to access it in tool handler. I need it because im changing access to certain things based on this authorization, so it changes the response i'm giving.
Getting a session ID in handler would be enough to match it in my case, however seems like more general issue to be able to get more info in tool handler about the request that just args.
Or is it a design choice that only this small set of information should be available?
I understand that tools probably should be 'transport-agnostic' so direct access to headers is probably a no-go, however some way to pass additional information would be nice.

[big-mouth-cn]

I want to transmit user information through SSE, but I have tried both headers and env and failed.

[abunet]

same problemi here. the tools handler seems to have an Exchange. from the exchange we can get session information. but howto store in session request info (headers. querystrings. pathinfo) and read them in tools handler

[Randgalt]

This library is currently unusable for us because of this. I'd hate to have to write my own library but that may be required. Further, my attempts to use Thread Locals failed because of the apparent deep async-ness of this library.

[big-mouth-cn]

#233

[Kehrlann]

@Randgalt In 0.11.0 we have added support for thread-locals, in #371. You must use McpSyncServer. In the SyncSpec, ensure you apply .immediateExecution(true).

Thread-local propagation is not supported in McpAsyncServer; you'd have to use the Reactor context.

[Randgalt]

Thread-local propagation is not supported in McpAsyncServer; you'd have to use the Reactor context.

Thank you, but the we've moved on tbh. We have our own implementation now that doesn't rely on libs such as Reactor. Cheers.