auth-tool-cloudbase

CloudBase login strategy configuration validation confirms which specific login methods are enabled across your environment. It inspects active provider states to ensure the correct Web or client auth flow can proceed without stalling due to misconfigured authentication settings.

Enable or disable CloudBase auth providers by applying provider strategy patching through auth management queries. This adjusts active login methods like WeChat or Google directly within your environment configuration before any platform-specific auth implementation begins.

A publishable key is required for CloudBase client-side authentication readiness. Verifying frontend readiness assets ensures the required publishable-key prerequisites are available before implementing app-side auth wiring to prevent stalled login flows.

CloudBase auth configuration routes incorrectly when management-side and app-side logic mix. Correct MCP tool boundaries separate auth management queries and provider strategy patching from app-side configuration, directing tasks to Web, mini program, or backend skills instead.

MCP auth tools for CloudBase platform routing are limited to management-side queries and provider strategy patching. They should not handle raw app-side configuration routing, which must be directed to platform-specific skills like Web, mini program, or Node backend boundaries.