Tencent CloudBase

Tencent CloudBase Plugin

The universal Tencent CloudBase plugin — gives AI coding agents direct access to CloudBase platform capabilities: AI models, authentication, NoSQL/PostgreSQL databases, cloud functions, cloud storage, CloudRun backend services, WeChat Mini Program integration, and more.

What this plugin provides

• Skills — Granular, scenario-driven skill files (synced from TencentCloudBase/skills) that activate when your project needs database operations, authentication setup, cloud function deployment, AI model integration, or Mini Program development.
• MCP server — The cloudbase-mcp server exposes tools for environment management, data operations, function deployment, and platform config.

The skills/ directory is a generated artifact — do not edit files in it directly. They are synced from TencentCloudBase/skills@main via scripts/sync-cloudbase-plugin-skills.mjs.

Skill-inject matching data (promptSignals / retrieval / priority) lives in skill-metadata.json (sibling of skills/, not overwritten by sync). When landing a new plugin skill, copy skill-metadata.template.json into skill-metadata.json using the skills directory name as the key, then run npm run build:skill-manifest from the monorepo root.

One-click install (recommended)

Install via the dedicated plugin repository (Open Plugin Spec):

npx plugins add TencentCloudBase/cloudbase-plugin

This works with Claude Code, Cursor, Codex, and other hosts that support the Open Plugin Specification. The dedicated repo is auto-synced from this directory (without marketplace.json).

Quick start per host

Use these host-native marketplace flows when you prefer IDE-specific install paths instead of npx plugins add.

Codex

Add the CloudBase marketplace, then install the plugin:

# Add the marketplace (do this once; sparse avoids full-repo clone)
codex plugin marketplace add TencentCloudBase/CloudBase-MCP --ref main \
  --sparse .agents/plugins \
  --sparse plugin

# Install plugins from the marketplace
codex plugin add cloudbase@tencent-cloudbase

Verify the marketplace is active:

codex plugin list --marketplace tencent-cloudbase

To update the plugin when new skills are released, upgrade the marketplace:

codex plugin marketplace upgrade tencent-cloudbase

Claude Code

Claude Code also supports plugin marketplaces. Add this repository as a marketplace, then install the plugin:

# Interactive command inside Claude Code
/plugin marketplace add TencentCloudBase/CloudBase-MCP
/plugin install cloudbase@tencent-cloudbase

For non-interactive setup:

claude plugin marketplace add TencentCloudBase/CloudBase-MCP
claude plugin install cloudbase@tencent-cloudbase

Claude Code reads the marketplace from .claude-plugin/marketplace.json.

Cursor

This repository includes Cursor Marketplace manifests (.cursor-plugin/marketplace.json and per-plugin .cursor-plugin/plugin.json).

Until the official Cursor Marketplace listing is approved, prefer:

npx plugins add TencentCloudBase/cloudbase-plugin -y --scope user --target cursor

To submit / update the official listing, use https://cursor.com/marketplace/publish with this repository URL.

OpenClaw

Add the cloudbase MCP server to your project:

// .mcp.json (project root) or ~/.mcp.json (global)
{
  "mcpServers": {
    "cloudbase": {
      "command": "npx",
      "args": ["npm-global-exec@latest", "@cloudbase/cloudbase-mcp@latest"],
      "env": { "INTEGRATION_IDE": "Claude" }
    }
  }
}

For granular skill activation, skills are available under plugin/cloudbase/skills/ in the CloudBase-MCP repository. Copy the ones you need into your project's .claude/skills/ directory.

Gemini CLI

Install via the CloudBase GitHub repository:

# Clone and link the extension
git clone https://github.com/TencentCloudBase/CloudBase-MCP
gemini extensions link "$(pwd)/CloudBase-MCP/plugin/cloudbase"

The extension auto-discovers skills from skills/ and registers the cloudbase MCP server via gemini-extension.json.

OpenCode

Add to your OpenCode config:

// .opencode.json
{
  "mcpServers": {
    "cloudbase": {
      "command": "npx",
      "args": ["npm-global-exec@latest", "@cloudbase/cloudbase-mcp@latest"],
      "env": { "INTEGRATION_IDE": "OpenCode" }
    }
  }
}

CodeBuddy

CodeBuddy uses the config/codebuddy-plugin/ packaging in this repository — an all-in-one skill bundle derived from the same source skills in config/source/skills/. The plugin/cloudbase/skills/ directory provides the same content in Codex-compatible granular form.

To install in CodeBuddy, follow the setup instructions in doc/ide-setup/ or run the MCP Setup tool in CodeBuddy Code.

ZCode

ZCode 3.4.1+ ships a built-in cloudbase-skills plugin under Settings → Plugins → Developer Tools. You can also add CloudBase MCP manually under Settings → MCP Servers.

See doc/ide-setup/zcode.mdx for the full guide.

Kimi Code

Kimi Code supports CloudBase via its Curated plugin marketplace (/plugins). Search for Tencent CloudBase (id: cloudbase) and install. See doc/ide-setup/kimi-code.mdx.

Kimi Work

Kimi Work ships CloudBase as a built-in plugin under Settings → Plugins. Enable it from the plugins panel. See doc/ide-setup/kimi-code.mdx.

Relationship with CloudBase Sites

	Tencent CloudBase (this plugin)	CloudBase Sites (plugin/cloudbase-sites)
Purpose	Platform capabilities: AI, auth, DB, functions, storage	Vite-based site creation, preview, versioning, deploy
Skills	26+ granular skills from TencentCloudBase/skills	Single runtime orchestration skill
CLI	None (uses cloudbase-mcp tools)	cloudbase-sites binary for preview/save/deploy
Use case	Add CloudBase to any project	Bootstrap, preview, and ship Vite web apps

The two plugins complement each other: use CloudBase Sites for the site lifecycle (create, preview, deploy, rollback) and Tencent CloudBase for everything else (auth, database, functions, AI models, storage).

Updating skills

Telemetry

Plugin telemetry is on by default and mirrors Vercel's lightweight DAU model, uploaded via the same Tencent Beacon (灯塔) endpoint used by cloudbase-mcp.

What is collected:

• toolkit_plugin_dau: at most once per UTC day when a SessionStart hook runs
• toolkit_plugin_first_use: once per local user profile on first successful report
• pluginVersion: included on each event so usage can be grouped by plugin version
• login_uin: the CloudBase account uin, read from the local login state (~/.config/.cloudbase/auth.json) so plugin usage can be attributed to an account
• envId: the environment id recorded in that same local login state, when present

Both attribution fields are read from that local file only — no network call and no credential exchange. Nothing else in it (refresh tokens, temporary secret keys) is read, logged or sent, and either field falls back to unknown when unavailable.

What is not collected: prompt text, file paths, project names, credentials or secrets, tool-call contents, or skill-injection details.

Disable:

export CLOUDBASE_PLUGIN_TELEMETRY=off

CLOUDBASE_MCP_TELEMETRY_DISABLED=true also disables plugin telemetry. Local throttle files live under ~/.config/cloudbase-plugin/ (dau-stamp, first-use-stamp) and are written only after a successful Beacon upload.

Skill sync

Skills are auto-synced from TencentCloudBase/skills@main. To update manually:

node scripts/sync-cloudbase-plugin-skills.mjs

Check for drift without modifying:

node scripts/sync-cloudbase-plugin-skills.mjs --check

A CI workflow runs the sync on schedule and commits changes automatically.