What this package is
@cloudbase/cloudbase-mcp is the npm distribution of the CloudBase MCP Server. It is one piece of the Toolkit:
| Piece | Role |
|---|
| Plugin | Installs MCP + Skills + Hooks together |
| Agent Skills | Scenario skills toward workable CloudBase practice |
| MCP (this package) | Tools the agent calls to act on your CloudBase environment |
Prefer Plugin when your IDE supports it. Use this package alone when you only need MCP config.
Full Toolkit narrative, related repos, and IDE matrix: repository README.
Quick start
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}
First prompts:
Use CloudBase Skills to build a todo app with login, database and permissions, then deploy
You need a CloudBase environment and should confirm sensitive actions the AI proposes.
Other install paths
| Path | When |
|---|
Official MCP Registry io.github.TencentCloudBase/cloudbase-mcp | Discover via registry search=cloudbase |
npx plugins add TencentCloudBase/cloudbase-plugin | Open Plugin Spec tools |
npm i -g @cloudbase/cli && tcb ai | CloudBase AI CLI configures many IDEs |
| Marketplace / built-in plugin | Claude Code, Codex, CodeBuddy, WorkBuddy, Kimi Code, Kimi Work, ZCode, etc. |
Connection modes
Remote (recommended): your IDE connects over HTTP to Tencent Cloud MCP. No local Node, and interactive clients finish authorization in the browser.
| Site | MCP endpoint |
|---|
| China (domestic) | https://tcb-api.cloud.tencent.com/mcp/v1 |
| International | https://tcb-api.tencentcloud.com/mcp/v1 |
Pick the endpoint matching the site your environment lives in—the two sites use separate accounts and credentials.
Local: runs npx @cloudbase/cloudbase-mcp@latest on your machine—full features, including local filesystem upload and template download. Requires Node.js v18.15.0+.
{
"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>"
}
}
}
}
Remote auth takes one of two paths:
- OAuth (interactive, recommended): add the URL only—your IDE opens the browser for login and consent, so no keys land in config files.
- Static credentials (CI/CD): add
env_id with the X-TencentCloud-* headers above.
Remote trade-off: local-filesystem features (upload, template download) are unavailable, and the international site does not yet expose NoSQL tools.
Remote URLs accept site for one case only—a China-site environment in ap-singapore, where the region is ambiguous—plus enable_plugins / disable_plugins (comma-separated). Canonical plugin names: see src/server.ts in this package (e.g. env, database, functions, hosting, storage, pg_database, cloudrun, logs).
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 / fastest start | Remote URL (OAuth) |
| Need local file features | Local npx |
| CI / automation | Remote + static credentials |
| Self-hosted MCP | Cloud Mode required |
Site & region
Set TCB_SITE (domestic / intl) to select the login/credential site, and TCB_REGION for API routing. The domestic and international sites are separate account systems. ap-singapore exists on both, so domestic-site Singapore users must set TCB_SITE=domestic; otherwise it defaults to intl. Project-level .cloudbase/project.json ({ site, region, envId }) is also supported.
In remote mode the site is determined by the endpoint host itself—tcb-api.cloud.tencent.com is the China site, tcb-api.tencentcloud.com is the international site—and there is no site query parameter to set. This holds for a China-site environment in ap-singapore too: keep using the China-site endpoint. Self-hosted Cloud Mode deployments can still use the TCB_SITE environment variable.
Capabilities
Typical backend work in your environment (confirm critical steps):
- Database: PostgreSQL and document DB, data models, CRUD, permissions
- Compute: cloud functions / Cloud Run—author, deploy, invoke, debug
- Auth & storage: login methods, object storage, permission linkage
- Release & ops: static hosting / Mini Program publish; logs and redeploy
Tool catalog: MCP tools · tools.json
IDE config snippets
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; manual MCP config is usually unnecessary.
Others: IDE setup.
Docs
License
MIT · TencentCloudBase
