MCP OAuth Support and Multi-Tenancy

[sibblegp]

Describe the feature

Hi. So we are a SaaS personal assistant AI for consumers. We currently integrate with APIs directly and not use MCP. Why? You have to launch the MCP instance at the time of the system starting and it is only connected to a single user. We cannot adjust the API key or any type of authorization so it can support multiple users like we can by adjusting an API key by calling an API directly. I.e. it's single-tenancy as opposed to multi-tenancy.

So I have two requests:

1. Support specifying the authorization key or method to an MCP server during runtime so it can be changed. This would allow multi-user support. If this is possible I'd love to know how.

2. Support OAuth authorization for MCP servers (this may be possible but I don't know how).

Thanks!

[seratch]

Support specifying the authorization key or method to an MCP server during runtime so it can be changed. This would allow multi-user support. If this is possible I'd love to know how.

Our current recommendation is to instantiate an agent and its required MCP servers on-demand when you run the logic for a user. The reason is that if an MCP server requires an authorization header even for the init / list tools requests, you won’t be able to reuse a single MCP server instance across tenants or customers (because the responses could be different per user). I understand you want to set up all the tools during system bootstrap, but if I’m reading this correctly, the MCP protocol for your use case may not work this way for all scenarios for the reason above while initializing all first works for the MCP tools just for your own personal use.

Also, another approach would be to have a thin function tool as a wrapper of MCP server tools. With this way, you can pass user_id as context to the function tool and you can resolve the user's user token for calling MCP server tools. This means you don't pass mcp_servers to an Agent instance. Instead, you pass the wrapper function tools to the agent.

Support OAuth authorization for MCP servers (this may be possible but I don't know how).

Issuing OAuth/OIDC tokens is out of scope for this SDK. You can implement the user-facing OAuth flow in your own service: redirect users to the provider’s consent page, handle the callback securely, and store/rotate tokens in your backend. This SDK is not a web framework and does not provide browser-based OAuth utilities, so your service should inject the resulting access token (for example, as an Authorization header) when instantiating or invoking MCP tools.

Hope this helps!

[sibblegp]

Those are both great responses and suggestions. Thanks!