云基MCP

Prerequisites

• Node.js v18.15.0+
• A CloudBase environment
• An AI tool that supports Plugin / Skills / MCP

Install & connect

Setup options

1. Plugin (when the tool supports it) npx plugins add TencentCloudBase/cloudbase-plugin 2. CloudBase AI CLI npm i -g @cloudbase/cli && tcb ai 3. Manual MCP (write the IDE config file)

<details> <summary>Cursor (.cursor/mcp.json)</summary>

{
  "mcpServers": {
    "cloudbase": {
      "command": "npx",
      "args": ["@cloudbase/cloudbase-mcp@latest"]
    }
  }
}

</details>

<details> <summary>WindSurf (.windsurf/settings.json)</summary>

{
  "mcpServers": {
    "cloudbase": {
      "command": "npx",
      "args": ["@cloudbase/cloudbase-mcp@latest"]
    }
  }
}

</details>

<details> <summary>CodeBuddy</summary>

CloudBase is built in (MCP / Skills); manual config is usually unnecessary.

You can also install via the plugin marketplace: see the CodeBuddy setup guide.

</details>

Others: IDE setup guide.

Quick start

Example

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

FAQ

<details> <summary>How is this different from Vercel / Netlify?</summary>

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.

</details>

<details> <summary>Can I use this without a GUI IDE?</summary>

Yes. Any tool that can configure an MCP Server or install the matching Plugin / Skills works—including Claude Code, Gemini CLI, OpenCode. Support list

</details>

<details> <summary>Where does my code go?</summary>

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.

</details>

<details> <summary>Is self-hosting the MCP server safe?</summary>

Local npx is equivalent to running tools yourself. For remote hosts, set CLOUDBASE_MCP_CLOUD_MODE=true to disable local file/process tools. Tencent Cloud hosted HTTP includes this protection.

</details>

<details> <summary>Cost?</summary>

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

</details>

<details> <summary>Login says environment does not exist?</summary>

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

</details>

<details> <summary>Domestic site env at ap-singapore is treated as international?</summary>

Both the domestic site (cloud.tencent.com) and the international site (tencentcloud.com) offer the ap-singapore region, so region alone is ambiguous. Without an explicit site, MCP defaults to intl for ap-singapore (backward compatible). Domestic-site Singapore users must set TCB_SITE=domestic (together with TCB_REGION=ap-singapore) in the MCP env, or add a .cloudbase/project.json at 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-slot auth.json is read as domestic and migrated on first write.

Hosted mode: add site=domestic to 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 MCP env block for HTTP servers).

</details>