chore: Clarify MCP OAuth token handling in UI

docs/my-website/docs/mcp.md

@@ -502,7 +502,7 @@ Your OpenAPI specification should follow standard OpenAPI/Swagger conventions:
 
 LiteLLM v 1.77.6 added support for OAuth 2.0 Client Credentials for MCP servers.
 
-This configuration is currently available on the config.yaml, with UI support coming soon.
+You can configure this either in `config.yaml` or directly from the LiteLLM UI (MCP Servers → Authentication → OAuth).
 
 ```yaml
 mcp_servers:

ui/litellm-dashboard/src/components/mcp_tools/create_mcp_server.tsx

@@ -663,7 +663,7 @@ const CreateMCPServer: React.FC<CreateMCPServerProps> = ({
                 </Form.Item>
                 <div className="rounded-lg border border-dashed border-gray-300 p-4 space-y-2">
                   <p className="text-sm text-gray-600">
-                    Complete the OAuth authorization flow to fetch an access token and store it as the authentication value.
+                    Use OAuth to fetch a fresh access token and temporarily save it in the session as the authentication value.
                   </p>
                   <Button
                     variant="secondary"

ui/litellm-dashboard/src/components/mcp_tools/mcp_server_edit.tsx

@@ -553,7 +553,7 @@ const MCPServerEdit: React.FC<MCPServerEditProps> = ({
                   />
                 </Form.Item>
                 <div className="rounded-lg border border-dashed border-gray-300 p-4 space-y-2">
-                  <p className="text-sm text-gray-600">Use OAuth to fetch a fresh access token and save it as the authentication value.</p>
+                  <p className="text-sm text-gray-600">Use OAuth to fetch a fresh access token and temporarily save it in the session as the authentication value.</p>
                   <Button
                     variant="secondary"
                     onClick={startOAuthFlow}