What it takes off you is moving between consoles: the database, the functions, the storage bucket, the hosting site, the gateway routes and the auth configuration are all reachable from the same session, in the order you actually build them. Read and write are separate calls in every domain, and the operations that spend money or destroy data will not run without a confirmation flag — which is what makes handing the whole surface to an agent survivable.
Tencent CloudBase's own MCP server. Calls are split into read and write pairs per domain, and everything acts on the one environment you bind after logging in. It runs locally from npm, or you point the client at Tencent's hosted endpoint instead.
- Login — interactive or with an API key — and binding to the environment every other call then acts on
- Environments listed, inspected and their security domains managed, plus creation, plan changes and renewal, each requiring explicit confirmation because each costs money
- NoSQL collections and indexes created, inspected and dropped, and records queried, inserted, updated, deleted or upserted with the usual operators
- Data models listed and inspected, and new ones created from a Mermaid class diagram
- PostgreSQL read-only SQL, object inspection and metadata, with writes going through a migration flow that records a versioned file rather than an ad-hoc statement
- MySQL provisioned, destroyed, queried read-only, and written to with SQL and DDL
- Cloud functions listed with their detail, logs, layers, triggers and code download URL, then created, updated, invoked, and given cron timer triggers
- Static hosting: files listed and searched, builds uploaded, index and error pages and routing rules set, custom domains bound and unbound
- Object storage listed, uploaded, downloaded and deleted, with temporary signed URLs whose lifetime you set
- Cloud Run services listed and deployed, initialised from a template, run locally, reconfigured without redeploying, and deleted
- HTTP gateway routes created, updated, enabled, disabled and deleted, mapping paths to functions, Cloud Run, static hosting or a lightweight server
- Application-side auth configuration: login methods, providers, clients, publishable keys and API keys
- Web applications deployed to their own subdomain, with build status polled by build id and the build log available on failure
- Resource permissions, roles, members and application users read and changed
- CLS log search across services, and a check on whether the log service is switched on
- Remote agents listed, created, updated and deleted, with their logs
- Project templates for React, Vue, WeChat mini-program, UniApp or editor rules alone, downloaded and deployed
- A knowledge-base search over CloudBase skill documents, OpenAPI specs, official documentation and a vector index
- A remote file downloaded into the project at a relative path, and a generic control-plane API call for what the named tools do not cover
A Tencent CloudBase account and an environment bound — `auth` logs in and binds it, and the other calls act on cloud resources only once it has. Locally that is npx and `@cloudbase/cloudbase-mcp@latest`; to skip the local install, point the client at https://tcb-api.cloud.tencent.com/mcp/v1 with your environment id and a Tencent Cloud SecretId and SecretKey in the X-TencentCloud-SecretId and X-TencentCloud-SecretKey headers. Environment creation, plan changes and renewal cost money and refuse to run without an explicit confirmation. PostgreSQL and NoSQL environments use different storage tools, and schema changes on PostgreSQL go through the migration flow rather than a direct statement.
One command — npx @cloudbase/cloudbase-mcp@latest