Add support for MCP authentication via a centrally managed OAuth application

What is the challenge?

• The current MCP authentication flow supports OAuth through dynamic client registration, which works for individual end-user connections but does not support a centralized OAuth application model.

• Some organizations need MCP access to be brokered through a single, centrally managed OAuth application so they can enforce consistent authentication, authorization, auditing, and policy controls across all users and tools.

What is the impact?

• Without support for a centralized OAuth approach, teams with stricter security and governance requirements may be unable to adopt MCP usage

Describe your idea.

• Add support for MCP authentication via a centrally managed OAuth application, in addition to the existing dynamic client registration flow.

• Allow organizations to register and use a single approved OAuth client for MCP access, so requests can be authenticated through a managed enterprise-controlled path.