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 · Changelog · Issues

Recent updates

v2.35.x (2026-10)

• Hosted / Auth: each hosted MCP request runs on its own transport with client metadata cached per credential, and a project-level credential now takes precedence over the account login state
• Tools / Skills: MySQL provisioning is retired from the tool surface; every skill package ships a LICENSE.md next to SKILL.md; a new MCP reference skill documents the remote endpoints, the plugin flags and the tool schemas
• Feedback: prepareFeedback returns the repository's new-issue page instead of an auto-filled error report, and a hosted server now enables the same default plugin set as a local one
• Onboarding / Docs: every initialize response now carries server instructions — the call to make first, the order a first run needs, and prompts that can be copied verbatim; the remote setup docs now lead with OAuth, so the URL alone is the configuration and a key pair is the CI path

v2.34.x (2026-09)

• i18n / IDE: full tool-copy localization with an instance-level lang, plus auth site / region params so international-site login and region routing resolve correctly
• Cloud API: callCloudApi service allowlist widened to 57 with built-in version mapping (multi-version services such as tke / mongodb / vod require an explicit version)
• Deploy / Env: new appBuild tool with hosting build neutralization; queryEnv reports the region actually applied and domains honors a passed envId
• Skills / Docs: skill fallback reads now point at the official distribution repo with a references address list; SDK-first database decision gate for cloudrun; site doc links moved to the current Markdown addresses; post-deployment share offered after delivery in the expert packs and the deploy skills (opt-in, redacted, at most once)
• Deploy / Apps: the cloud upload channel now completes end to end (deployApp accepts the timestamp getUploadUrl returns, getBuildLog accepts the build ID a deploy returns), and gateway route creation verifies the upstream exists before writing
• Skills / Context: new PostgreSQL access-pattern best-practices skill (batching, indexes, RLS role gating, launch capacity); searchKnowledgeBase's inline skill / OpenAPI catalogs now load on demand, cutting the 43-tool surface by 9.1% on every tools/list
• Runtime / Hosting: CloudRun Function mode must not bind PORT (the function framework does) and gets a credential decision gate naming CLOUDBASE_APIKEY; hosting paths and prefixes are normalized so a leading slash can no longer read as an empty directory
• Connectors: the international-site WorkBuddy connector (cloudbase-intl) is built from the same config/source/** corpus as the domestic one — remote streamableHttp with standard MCP OAuth instead of local stdio, with China-site hosts rewritten to their international equivalents

Releases · Star · 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:

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:

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

Fastest way to get started

Copy this AI prompt into your AI IDE. The agent reads skill.md and completes the setup:

Set up CloudBase for me:
1. Open https://docs.cloudbase.net/skill.md and complete the setup following its instructions.
2. Tell me when you're done, and suggest the most relevant next step.

Plugin

npx plugins add TencentCloudBase/cloudbase-plugin

Details and IDE differences: AI plugin docs.

MCP only

{
  "mcpServers": {
    "cloudbase": {
      "command": "npx",
      "args": ["@cloudbase/cloudbase-mcp@latest"]
    }
  }
}

Remote HTTP, self-hosted Cloud Mode, and plugin scoping: Install & connect.

First prompts

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.

Supported AI IDEs

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

1. Plugin (when the tool supports it)
   npx plugins add TencentCloudBase/cloudbase-plugin
2. CloudBase AI CLI
   npm i -g @cloudbase/cli && tcb ai
3. 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 unnecessary.

You can also install via the plugin marketplace: see the CodeBuddy setup guide.

Others: IDE setup guide.

MCP connection modes

Remote (recommended): your IDE connects over HTTP to Tencent Cloud MCP. No local Node, and interactive clients finish authorization in the browser.

Pick the endpoint matching the site your environment lives in—the two sites use separate accounts, consoles, and credentials.

OAuth (interactive, recommended): the URL is the whole configuration. Your IDE opens the browser for login and consent, and you pick the environment there—no keys in the config file, and nothing to rotate.

{
  "mcpServers": {
    "cloudbase": {
      "type": "http",
      "url": "https://tcb-api.cloud.tencent.com/mcp/v1"
    }
  }
}

Static credentials (for a client without OAuth, and for CI/CD): append env_id and a key pair created on the same site as the endpoint.

{
  "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>"
      }
    }
  }
}

A static key pair stays valid until it is rotated or deleted; an OAuth session ends when you log out. Use the static form only where the browser flow is impossible—and keep it out of a repository.

Local: runs npx @cloudbase/cloudbase-mcp@latest on your machine—full features, including local filesystem upload and template download.

Remote trade-off: local-filesystem features (upload, template download) are unavailable, and the international site does not yet expose NoSQL tools.

Remote URLs also accept site (domestic / intl, only needed for a China-site environment in ap-singapore, where the region is ambiguous), plus enable_plugins / disable_plugins to trim tools. Canonical names live in mcp/src/server.ts.

Remote MCP E2E (official SDK client): npm run test:hosted-mcp:e2e — see tests/hosted-mcp-e2e/README.md for apikey/OAuth modes, TLS-insecure staging, and env vars. Missing credentials skip (exit 0).

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.

Example

Online Gomoku: describe the need; get Web + cloud database / realtime and deploy.
Demo: Gomoku · More: tutorials

Docs

• MCP tools (tools.json)
• Getting started
• IDE setup
• AI plugins
• Templates
• FAQ

FAQ

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.

Yes. Any tool that can configure an MCP Server or install the matching Plugin / Skills works—including Claude Code, Gemini CLI, OpenCode. Support list

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.

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 remote HTTP includes this protection.

The Toolkit (including MCP) is open source under MIT. CloudBase has free quotas; usage beyond that is billed—see billing.

Confirm an environment exists and is healthy in the console, then login again and pick the right one.

Both the domestic site (cloud.tencent.com) and the international site (tencentcloud.com) offer the ap-singapore region, so region alone is ambiguous. Without an explicit site, MCP defaults to intl for ap-singapore (backward compatible). Domestic-site Singapore users must set TCB_SITE=domestic (together with TCB_REGION=ap-singapore) in the MCP env, or add a .cloudbase/project.json at the project root:

{ "site": "domestic", "region": "ap-singapore", "envId": "your-env-id" }

Credentials are stored per site (credential.domestic / credential.intl) so domestic and international logins can coexist; legacy single-slot auth.json is read as domestic and migrated on first write.

Remote mode: nothing extra to pass — the endpoint host decides the site (tcb-api.cloud.tencent.com = China site, tcb-api.tencentcloud.com = international site), and there is no site query parameter. This also covers a China-site environment located in ap-singapore: keep using the China-site endpoint.

Community

Activity

Contributors

MIT · TencentCloudBase