auth-tool-cloudbase

Configure and manage authentication providers in CloudBase web applications.

1|3|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Soltus/encv-go --skill auth-tool-cloudbase-soltus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-tool-cloudbase
Source: https://github.com/Soltus/encv-go/tree/main/.cloudbase-mcp/web-template/.claude/skills/auth-tool
Command: npx skills add https://github.com/Soltus/encv-go --skill auth-tool-cloudbase-soltus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires CloudBase SDK, MCP tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of configuring and managing authentication providers for web applications on CloudBase, enabling various login methods like SMS, Email, WeChat, and more.

Core Features & Use Cases

  • Manage Authentication Providers: Enable or disable login methods such as SMS, Email, WeChat, Google, and more.
  • Provider Settings Configuration: Customize settings for each authentication provider through MCP tools callCloudApi.
  • Scalable Authentication Management: Efficiently handle multiple authentication providers for scalable web applications.

Quick Start

To get started, run the command 'encv --login-strategy --env <env-id>' to query current login configuration.

Frequently Asked Questions about auth-tool-cloudbase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure CloudBase authentication providers for a web application?

Configure CloudBase authentication providers by enabling and customizing login methods like SMS, Email, WeChat, and Google through API calls. This process manages user access settings via MCP tools to establish web application login functionality.

What login methods are supported by CloudBase authentication?

CloudBase authentication supports SMS, Email, WeChat, and Google login methods. The system allows you to enable, disable, and customize settings for each authentication provider to facilitate scalable web application access.

Do I need an environment ID to manage CloudBase login configuration?

Yes, a CloudBase environment ID is required to manage login configuration. You must provide this environment identifier when querying current login strategies or modifying authentication providers through CloudBase API calls.

What is the best way to check current CloudBase authentication settings?

Check current CloudBase authentication settings by running the query command with your environment ID. This queries your active login configuration and returns the current state of your authentication providers.

Can I use MCP tools to customize CloudBase provider settings?

Yes, you can use MCP tools to customize CloudBase provider settings. Specifically, the `callCloudApi` MCP tool enables you to configure and manage individual authentication provider parameters effectively.

Why disable a login method in CloudBase web applications?

Disabling a login method in CloudBase web applications removes unused authentication providers. This restricts user access to only active channels, streamlining security and login management for your application.