CloudBase AI ToolKit

by tencentcloudbase

Not rated
GitHub

About

Go from AI prompt to live app in one click. CloudBase AI ToolKit is the bridge that connects your AI IDE (Cursor, Copilot, etc.) directly to Tencent CloudBase.

Details

Author
tencentcloudbase
Categories
Database, Infrastructure, Developer Tools, Cloud Service

Setup

Install CloudBase AI ToolKit in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/tencentcloudbase/CloudBase-AI-ToolKit

Follow the installation instructions in the repository README, then restart your MCP client.

What can you do with CloudBase AI ToolKit MCP?

- Database operations— Ask to create, query, or modify data in PostgreSQL or document databases, including CRUD and security rules.
- Cloud functions & Cloud Run— Author, deploy, invoke, and debug serverless functions or containerized services directly from chat.
- Auth & storage management— Configure login methods, manage object storage, and link permissions with data access.
- Release & operations— Publish static hosting or Mini Programs, inspect deployment logs viagetDeployLog, and redeploy when needed.
- Environment setup & login— Authenticate to your CloudBase environment and manage cross-region queries withcredential_scopeboundaries.

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

- CloudRun:getDeployLogfailures (CODING login / image deploy with no build) now rewrite togetProcessLog/getDeployRecordsnext steps instead of raw English errors

- Env: cross-region environment query and clearer credential-scope boundary for MCP auth
- Auth: drop redundantlogin_mode; keepcredential_scopeas the single credential boundary signal
- Release: Kimi plugin zip uses a whitelist-only, version-free asset name
- Kimi: plugin zip assembles sibling skills intoskills/cloudbase/references/so the archive stays self-contained and in sync with the manifest contract

- IDE: Kimi Code plugin (kimi.plugin.json) reuses shared CloudBase skills/MCP assets
- Release: pack Kimi plugin zip and attach it to GitHub Release assets automatically
- Auth UX: Kimi login via MCPauthdevice-code flow; routing skill loads domain knowledge on demand

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.

CloudBaseis 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.

Publishing and sync repos live underTencentCloudBase. 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 runnpx plugins addon the same tool.

Copy this AI prompt into your AI IDE. The agent readsskill.mdand 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.
npx plugins add TencentCloudBase/cloudbase-plugin

Details 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.

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.

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)

{ "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 theCodeBuddy setup guide.

Local(default):npxon 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 usesite(domestic/intl) to pick the login site (e.g. domestic-site Singapore needssite=domestic), plusenable_plugins/disable_pluginsto trim tools. Canonical names live inmcp/src/server.ts.

Self-hosted Cloud Mode: setCLOUDBASE_MCP_CLOUD_MODE=true(orMCP_CLOUD_MODE=true) so local file and process tools are disabled for remote callers.

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

- MCP tools(tools.json)
-
Getting started
-
IDE setup
-
AI plugins
-
Templates
-
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.

Localnpxis equivalent to running tools yourself. For remote hosts, setCLOUDBASE_MCP_CLOUD_MODE=trueto disable local file/process tools. Tencent Cloud hosted HTTP includes this protection.

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

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

Both the domestic site (cloud.tencent.com) and the international site (tencentcloud.com) offer theap-singaporeregion, so region alone is ambiguous. Without an explicit site, MCP defaults tointlforap-singapore(backward compatible). Domestic-site Singapore users must setTCB_SITE=domestic(together withTCB_REGION=ap-singapore) in the MCPenv, or add a.cloudbase/project.jsonat 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-slotauth.jsonis read asdomesticand migrated on first write.

Hosted mode: addsite=domesticto the hosted URL (https://tcb-api.cloud.tencent.com/mcp/v1?env_id=<env_id>&site=domestic), since the URL is the only place hosted mode can carry the site (there is no MCPenvblock for HTTP servers).

Full-stack backend platform MCP — provision apps, manage databases, deploy functions, and more.

A template for deploying a remote, authentication-free MCP server on Cloudflare Workers. Tools are defined directly in the source code.

Deploy Python functions as web apps. Type hints become UI, API, and shareable links. 32 MCP tools for deploy, run, storage, secrets, scheduling, versioning, and sharing.

A template for deploying a remote MCP server on Cloudflare Workers without authentication.

Introspect and query your apps deployed to Convex.

Core AWS MCP server providing prompt understanding and server management capabilities.

An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.

Create, build, deploy, and manage Netlify resources using natural language.

The Railway MCP Server enables natural language interaction with your Railway projects and infrastructure. Ask your IDE or AI assistant to create projects, deploy templates, manage environments, pull variables, redeploy services, and more.

The Shipyard CLI provides an MCP server for agents to manage Shipyard environments directly: by pulling logs, comparing branches, running tests, and stopping/starting environments..

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.