CloudBase MCP
CloudBase MCP is an MCP server published by Tencent CloudBase; its MCP spec-revision support has not been verified yet. It is the first-party server from Tencent CloudBase. Last verified 2026-09-03.
Does CloudBase MCP support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision CloudBase MCP supports (as of 2026-09-03).
Is CloudBase MCP a first-party (official) MCP server?
Yes. CloudBase MCP is the first-party MCP server published by Tencent CloudBase (last verified 2026-09-03).
How do I connect to CloudBase MCP?
CloudBase MCP is available via a hosted remote endpoint at https://tcb-api.cloud.tencent.com/mcp/v1, the package npm:@cloudbase/cloudbase-mcp, the official MCP Registry under io.github.TencentCloudBase/cloudbase-mcp, the source repository at https://github.com/TencentCloudBase/CloudBase-AI-Toolkit. Authentication: api_key. Transports: streamable-http, stdio.
What tools does CloudBase MCP expose?
CloudBase MCP exposes 40 tools, including env, database, pg_database, functions, cloudrun, hosting (last verified 2026-09-03).
When were CloudBase MCP's facts last verified?
2026-09-03. Each fact on this page links to the sources used to verify it.
Which tools does CloudBase MCP expose?
40 tools verified.
envdatabasepg_databasefunctionscloudrunhostingstoragelogs
Tencent's first-party MCP server for CloudBase, its serverless backend platform. It exposes CloudBase operations as tools so an agent in an AI coding tool can work with document and PostgreSQL databases, cloud functions, Cloud Run services, object storage, static hosting and logs without leaving the editor. The tool surface is organized into plugins that can be enabled or disabled per connection.
Two access paths are documented. Locally the server runs over stdio from
npm:@cloudbase/cloudbase-mcp, which keeps filesystem-dependent features
such as template and upload handling. Tencent also hosts the server at
tcb-api.cloud.tencent.com/mcp/v1, reached over Streamable HTTP with an
env_id query parameter identifying the CloudBase environment and Tencent
Cloud API key headers for authentication; that path drops the local-file
features.
Authority is first-party on Tencent-controlled evidence: the product site
on tcb.cloud.tencent.com links the publishing GitHub organization, the
documentation on docs.cloudbase.net covers the MCP integration, and the
hosted endpoint runs on cloud.tencent.com. Spec-revision support is
unverified, because no surface names a revision and the hosted endpoint
requires credentials that a public probe does not have.
How was this verified, and what are the sources?
Verified · method: vendor-announcement
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.TencentCloudBase/cloudbase-mcp, fetched 2026-09-03 - version 2.32.5 updated 2026-09-01, package npm @cloudbase/cloudbase-mcp 2.32.5, remote streamable-http https://tcb-api.cloud.tencent.com/mcp/v1?env_id={env_id} - accessed
- Tencent CloudBase product site on Tencent's own domain, fetched 2026-09-03 - links the GitHub organization https://github.com/TencentCloudBase and presents MCP as a supported integration surface, establishing first_party authority for a server fronting Tencent CloudBase - accessed
- Package README in the monorepo's mcp/ directory, fetched 2026-09-03 - "MCP Server for Tencent CloudBase... Operate CloudBase from AI coding tools: login, databases, functions, storage, hosting, and logs"; documents the hosted endpoint with X-TencentCloud-SecretId and X-TencentCloud-SecretKey headers, and a local stdio mode via npx - accessed
- Repository metadata, fetched 2026-09-03 - TencentCloudBase/CloudBase-AI-Toolkit, MIT, 1,091 stars, last push 2026-09-03, not archived; the MCP server lives in the mcp/ subdirectory of this monorepo - accessed
- Tool catalog in the repository, fetched 2026-09-03 - states the server currently contains 40 tools, grouped by plugin (env, database, pg_database, functions, cloudrun, hosting, storage, logs and others) - accessed
- Endpoint probe 2026-09-03 - GET returned HTTP 405 with body {"jsonrpc":"2.0","error":{"code":-32000,"message":"Method not allowed."}}, and an uncredentialed server/discover POST returned HTTP 403 "Forbidden: Missing credentials"; the endpoint is live and credential-gated, and no protocol revision was negotiated - accessed