auth-tool-cloudbase

To configure CloudBase authentication providers, you inspect, enable, and update provider configurations across web, mini program, and native app environments. This includes managing login method toggles, sender configurations, and publishable keys to ensure secure login flows before client implementation.

A CloudBase authentication provider readiness check verifies that prerequisites like publishable keys and static domain configurations are met. It ensures login methods and sender settings are correctly patched so that authentication workflows function securely across your target platforms.

Yes, you can enable SMS and Email login methods for CloudBase using specified MCP tool paths. The configuration process supports patching login strategies, updating provider states, and describing current login configurations to coordinate frontend and backend authentication workflows.

CloudBase auth configuration supports enabling, disabling, and managing multiple providers including WeChat, Google, Anonymous, Username/Password, and SMS. It applies MCP tool boundaries to coordinate secure login flows across web, mini program, and native app platforms.

Publishable keys are required before implementing CloudBase login flows to satisfy provider readiness prerequisites. Managing these keys alongside static domain considerations ensures that authentication configurations are validated and secure prior to deploying client or backend auth workflows.