What features would you like to see added?

In order to support MCP servers in a multi user environment, it would be nice if the mcp oauth flow was available on the client.

More details

For example, if I am using a shared librechat instance and I use a tool via mcp which gives access to my google drive, I would like to:

• have the mcp server answer with 401 auth required ( because an access token with drive scope is required for my account )
• have librechat
  • manage the oauth flow in the UI ( not in the server logs as is the case now )
  • resend the request to the MCP server with the match Authorization header

It seems all the configuration is ready in librechat.yaml / mcpServers and the flow is completely implemented server side.
When we need a per-user oauth authentification we must rely on the MCP server support which might not be ideal:
the tool has to answer with an authorization url flow and convince the llm to present it to the user and click on it .., it also means that each tool manages its own tokens instead of having a centralization in librechat.
The "drive connect" in chatgpt ( and others ) seems cleaner, and is already perceived as a standard for users.

Which components are impacted by your request?

UI

Pictures

No response

Code of Conduct

• I agree to follow this project's Code of Conduct