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 · Changelog · Issues
v2.24.x (2026-07)
- Plugin: Open Plugin Spec;
npx plugins addfor MCP / Skills / Hooks - PostgreSQL: schema changes default to
applyMigration(explicitmigrationVersion) - Env & observability:
manageEnvcontract fixes; tool calls can attach client info
Releases · Star · Watch → Releases
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.
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 |
| cloudbase-sites-plugin | Sites plugin: Vite Web create & deploy | npx plugins add TencentCloudBase/cloudbase-sites-plugin |
| cloudbase-skills | Agent Skills collection | npx skills add TencentCloudBase/cloudbase-skills |
| 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.
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) |
npx plugins add TencentCloudBase/cloudbase-pluginDetails and IDE differences: AI plugin docs.
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}Hosted HTTP, self-hosted Cloud Mode, and plugin scoping: Install & connect.
Login to CloudBase
Use CloudBase Skills to build a todo app with login, database and permissions, then deploy
Skills 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.
| 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.
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.
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
- Node.js v18.15.0+
- A CloudBase environment
- An AI tool that supports Plugin / Skills / MCP
- 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)
Cursor (.cursor/mcp.json)
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}WindSurf (.windsurf/settings.json)
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}CodeBuddy
CloudBase is built in (MCP / Skills); manual config is usually unnecessary.
Others: IDE setup guide.
Local (default): npx on your machine—full features, including local filesystem upload/templates.
Hosted: IDE connects over HTTP to Tencent Cloud MCP; no local Node. Some local-file features are unavailable.
{
"mcpServers": {
"cloudbase": {
"type": "http",
"url": "https://tcb-api.cloud.tencent.com/mcp/v1?env_id=<env_id>",
"headers": {
"X-TencentCloud-SecretId": "<Tencent Cloud Secret ID>",
"X-TencentCloud-SecretKey": "<Tencent Cloud Secret Key>"
}
}
}
}Hosted URLs can use enable_plugins / disable_plugins. Canonical names live in mcp/src/server.ts.
Self-hosted Cloud Mode: set CLOUDBASE_MCP_CLOUD_MODE=true (or MCP_CLOUD_MODE=true) so local file and process tools are disabled for remote callers.
| Scenario | Suggestion |
|---|---|
| Personal | Local npx |
| Team / zero ops | Hosted HTTP |
| Self-hosted MCP | Cloud Mode required |
Online Gomoku: describe the need; get Web + cloud database / realtime and deploy.
Demo: Gomoku · More: tutorials
How is this different from Vercel / Netlify?
Those focus on shipping frontends or containers. CloudBase provides backend building blocks (database, auth, functions). The Toolkit lets AI tools use them in chat. Deploy is only part of the path.
Can I use this without a GUI IDE?
Yes. Any tool that can configure an MCP Server or install the matching Plugin / Skills works—including Claude Code, Gemini CLI, OpenCode. Support list
Where does my code go?
Deploy targets your own CloudBase environment. In local mode MCP runs on your machine; code need not leave until you deploy. Cloud traffic uses HTTPS.
Is self-hosting the MCP server safe?
Local npx is equivalent to running tools yourself. For remote hosts, set CLOUDBASE_MCP_CLOUD_MODE=true to disable local file/process tools. Tencent Cloud hosted HTTP includes this protection.
Cost?
The Toolkit (including MCP) is open source under MIT. CloudBase has free quotas; usage beyond that is billed—see billing.
Login says environment does not exist?
Confirm an environment exists and is healthy in the console, then login again and pick the right one.
| Docs | docs.cloudbase.net |
| Issues | GitHub Issues |
| Releases | Changelog |
