CloudBase AI Toolkit
AI writes the code. CloudBase runs the backend.
The CloudBase integration layer for AI coding tools: Plugin installs the stack, Skills steer how code is written, MCP operates databases, functions, storage, and deploys from chat.
English · 简体中文 · [Docs][docs] · [Changelog][changelog] · [Issues][github-issues-link]
[![][npm-version-shield]][npm-link] [![][npm-downloads-shield]][npm-link] [![][github-stars-shield]][github-stars-link] [![][github-forks-shield]][github-forks-link] [![][github-issues-shield]][github-issues-link] ![][github-license-shield] ![][github-contributors-shield] [![][cnb-shield]][cnb-link] [![][deepwiki-shield]][deepwiki-link]
</div>Recent updates
v2.25.x (2026-07)
- CloudRun / Gateway: VPC guidance when using TCP databases; Domain/Route with
upstreamResourceTypeand path transmission - CloudRun / Gateway: preserve remote VPC & env config on redeploy; prefer custom-domain access URLs after deploy
- Plugin: easier install via Open Plugin / marketplace packaging
- Env / Database: clearer billing summary when creating an env; SDK-first guidance instead of raw TCP database info
- Auth / Database: fix createApiKey false success; fail closed when a PG migration does not land
[Releases][changelog] · [Star][github-stars-link] · Watch → Releases
What it is
AI IDEs (Cursor, Claude Code, Codex, CodeBuddy, and others) are strong at generating code. What usually blocks you is the backend: schemas, permissions, functions, storage, environments, and release.
CloudBase is Tencent Cloud’s AI-native all-in-one backend (database, storage, auth, cloud functions, Cloud Run, and more). This repo is the Toolkit that connects that backend to AI tools:
| Piece | Role |
|---|---|
| Plugin | Installs MCP Server, Agent Skills, and Hooks together—less per-IDE wiring |
| Agent Skills | Scenario skills (Web / Mini Program / database / auth / functions, etc.) toward workable CloudBase practice |
| MCP | Login, query and change data, manage functions and hosting, read logs—from the conversation |
This repository ships the npm package @cloudbase/cloudbase-mcp, Skills, and AI plugins.
You still need your own CloudBase environment, and you should confirm sensitive actions the AI proposes. The Toolkit provides capability and path—not judgment.
Related repositories
Publishing and sync repos live under TencentCloudBase. Directly related to this Toolkit:
| Repository | Contents | Typical entry |
|---|---|---|
| CloudBase-AI-Toolkit (this repo) | MCP Server source; marketplace source for Claude Code / Codex | npx @cloudbase/cloudbase-mcp@latest |
| cloudbase-plugin | Open Plugin Spec publish repo (CI-synced): MCP + Skills + Hooks | npx plugins add TencentCloudBase/cloudbase-plugin · CNB fallback: npx plugins add https://cnb.cool/tencent/cloud/cloudbase/cloudbase-plugin.git |
| cloudbase-sites-plugin | Sites plugin: Vite Web create & deploy | npx plugins add TencentCloudBase/cloudbase-sites-plugin · CNB: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-sites-plugin.git |
| cloudbase-skills | Agent Skills collection | npx skills add TencentCloudBase/cloudbase-skills · CNB: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills.git |
| skills | Per-skill install catalog (also on skills.sh) | npx skills add tencentcloudbase/skills --skill <name> |
| awesome-cloudbase-examples | CloudBase examples and case studies | Browse / clone examples |
| OpenVibeCoding | Vibecoding template on CloudBase | Use as a project starter |
Prefer Plugin for the full stack; Skills alone when you only need knowledge constraints. For marketplace IDEs use this repo—do not also run npx plugins add on the same tool.
Quick start
Pick one default path for your tool.
| Your tool | Suggested path |
|---|---|
| Claude Code / Codex (native marketplace) | Add this repo as marketplace, then install the cloudbase plugin (plugin docs) |
| Open Plugin Spec tools | npx plugins add TencentCloudBase/cloudbase-plugin |
| Prefer one CLI for many tools | CloudBase AI CLI: npm i -g @cloudbase/cli && tcb ai |
| CodeBuddy / WorkBuddy / ZCode (built-in) | Use the IDE’s built-in CloudBase plugin or connector |
| Other MCP-capable IDEs | MCP config only (below) |
Plugin
npx plugins add TencentCloudBase/cloudbase-pluginDetails and IDE differences: AI plugin docs.
MCP only
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}Hosted HTTP, self-hosted Cloud Mode, and plugin scoping: Install & connect.
First prompts
Login to CloudBaseUse CloudBase Skills to build a todo app with login, database and permissions, then deploySkills shape structure and practice; MCP handles environment and resources. You should be able to verify data and APIs in your own environment—not only get local source files.
Supported AI IDEs
<img width="1200" alt="Supported AI IDEs" src="scripts/assets/ide-support-grid.png" />| Tool | Platform | Guide |
|---|---|---|
| CloudBase AI CLI | CLI | Guide |
| OpenClaw | CLI | Guide |
| WorkBuddy | Standalone IDE | Guide |
| ZCode | Standalone IDE (≥ 3.4.1 built-in) | Guide |
| Codex App | App | Guide |
| Cursor | Standalone IDE | Guide |
| WindSurf | IDE / plugins | Guide |
| CodeBuddy | Standalone IDE (built-in) | Guide |
| CLINE | VS Code plugin | Guide |
| GitHub Copilot | VS Code plugin | Guide |
| Trae | Standalone IDE | Guide |
| Tongyi Lingma | IDE / plugins | Guide |
| RooCode | VS Code plugin | Guide |
| Baidu Comate | Plugins | Guide |
| Augment Code | Plugins | Guide |
| Claude Code | CLI | Guide |
| Gemini CLI | CLI | Guide |
| Codex CLI | CLI | Guide |
| OpenCode | CLI | Guide |
| Qwen Code | CLI | Guide |
Full setup: IDE guides.
Capabilities
After setup, the AI can do typical backend work in your environment (confirm critical steps):
- Database: PostgreSQL and document DB, data models, CRUD, permissions and security rules
- Compute: author, deploy, invoke, and debug cloud functions / Cloud Run
- Auth & storage: login methods, object storage, permission linkage with data
- Release & ops: static hosting / Mini Program publish; inspect logs and redeploy
Fits Web, WeChat Mini Programs, and backend services. Platform overview: CloudBase docs.
Evaluation
Under controlled conditions, the same Todo application brief and frontend scaffold were used to compare two backend paths: a traditional cloud VM (self-managed runtime, process, and network exposure) and CloudBase (managed database, anonymous auth, and related backend services). An AI agent performed end-to-end development and verification. Given the model and task setup, the CloudBase path was more favorable in completion latency, token usage, and tool-call count. These outcomes are conditioned on the model, agent framework, and task definition, and should not be generalized beyond that scope.
Methods, data, and limits: Same-task evaluation: cloud VM vs CloudBase
Install & connect
Prerequisites
- Node.js v18.15.0+
- A CloudBase environment
- An AI tool that supports Plugin / Skills / MCP
Setup options
- Plugin (when the tool supports it)
npx plugins add TencentCloudBase/cloudbase-plugin - CloudBase AI CLI
npm i -g @cloudbase/cli && tcb ai - Manual MCP (write the IDE config file)
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}CloudBase is built in (MCP / Skills); manual config is usually unne
…