Possibility to configure MCP Client so it uses an existing OAuth Token

[dvag-joerg-winter]

Expected Behavior

Add a config (application.properties) that enables passing of an existing Token
An existing Token was aquired in the Host application (which includes MCP Client Starter) from an Authserver in a previous step, outside/before the use of ChatClient/MCP Client

Current Behavior

when understanding correctly from the single example here
https://github.com/Kehrlann/spring-ai-mcp-authorization-demo
MCP Client Starter seems to be dependent on an AuthorizationServer configuration to execute the first Auth-exchange itself (instead of just using&passing an existing token in the Hostapplication.

Context

MCP Auth Specification
MCP Client/Server version 1.0.1

[quaff]

PR #3949 allow to configure arbitrary HTTP header including Authorization: Bearer <access_token>.

[dvag-joerg-winter]

Hi @quaff !
is it possible for you to outline Spring AI's concept for this feature from a very high-level point of view?
(describing how the existing Token in the MCP-Client-hosting-App will probably be passed to the MCP-Client, no need to go into specifics.. just from the Applications point of view)

[quaff]

See #3948 (comment)