This merge request would help me too. I would like to forward the authorization headers from the user to the actual tool use. So that the tool request can be done "in the name" of the original user. The backend is filtering out data based on the users permissions so i can not just use a service account for that.

The addition of this feature is proposed by our team, the starting point is to strengthen the ability of mcp, and then the actual use of the process, we hope that he can be used as we use http network requests, you can isolate the user's request for business data and some of the system data, you can do more things, for example, we can add the header object to add sourceclient to determine the source of the user , you can add the header object auth_token to do the login credentials to pass , you can add any field to do the B-side of the user wants to do things , such as adding a parameter encryption field , you can do some of the anti-climbing mechanism and so on.

Hi There.

This is a much needed feature. We are linking our internal backoffice systems via an MCP SSE server to our Chat Clients. The user is therefore able to search in different backend systems. However we need to be able to isolate the user via a header. If we have that header available in the Tool/Resource context we can do a Search/Fetch API call on the backend with that specific user context and therefore only returning data which is accessible to that user.