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

Comment From: quaff

PR https://github.com/spring-projects/spring-ai/pull/3949 allow to configure arbitrary HTTP header including Authorization: Bearer <access_token>.