Model Context Protocol을 통해 데이터베이스, 함수, 스토리지, 호스팅을 포함한 Tencent CloudBase 환경을 운영합니다.
다른 이름 TencentCloudBase/CloudBase-AI-Toolkit, cloudbase-mcp, @cloudbase/cloudbase-mcp
- 스타
- 1,165
- Tools
- —
- 다운로드, 30일
- 195,478
- 최신 버전
- 2.37.6
- 마지막 커밋
- 2026년 11월 15일
- 라이선스
- MIT
CloudBase MCP란?
CloudBase은(는) MCP server입니다. Model Context Protocol을 통해 데이터베이스, 함수, 스토리지, 호스팅을 포함한 Tencent CloudBase 환경을 운영합니다.
프로젝트 README에서 생성된 요약
CloudBase MCP server 정보
CloudBase는 Model Context Protocol을 사용하여 AI 코딩 도구에서 Tencent CloudBase 환경을 직접 관리할 수 있는 방법을 제공합니다. 개발자는 데이터베이스, 클라우드 함수, 스토리지, 호스팅과 같은 클라우드 리소스와 상호작용할 수 있습니다. 이 server는 npx를 통한 로컬 실행과 중국 또는 글로벌 사이트를 위한 HTTP 엔드포인트를 통한 remote 연결 모드를 모두 지원합니다.
사용자는 브라우저 기반의 간편한 인증을 위한 대화형 OAuth를 사용하거나, 자동화된 CI/CD 워크플로우를 위한 정적 자격 증명을 통해 연결할 수 있습니다. 로컬 모드는 로컬 파일 시스템 업로드 및 템플릿 다운로드를 포함한 모든 기능을 제공하며, remote 모드는 속도와 보안에 최적화되어 있습니다. 이 server에는 파괴적인 작업에 대한 특정 확인 대화 상자와 민감한 키를 작성할 때 실수로 발생하는 전사 오류를 방지하기 위한 자격 증명 가드와 같은 안전 메커니즘이 포함되어 있습니다.
활용 사례
- 1풀스택 애플리케이션 배포AI에게 데이터베이스와 권한이 포함된 할 일 관리 앱을 구축하도록 요청한 다음, 이를 클라우드에 배포합니다.
- 2CI/CD를 통한 클라우드 인프라 자동화정적 자격 증명을 사용하여 자동화된 클라이언트가 브라우저 상호작용 없이 환경을 관리할 수 있도록 합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
CloudBase MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 CloudBase MCP 설치
$ claude mcp add cloudbase-mcp -- npx -y @cloudbase/cloudbase-mcpCursor에 CloudBase MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"cloudbase-mcp": {
"command": "npx",
"args": [
"-y",
"@cloudbase/cloudbase-mcp"
]
}
}
}VS Code에 CloudBase MCP 설치
.vscode/mcp.json
{
"servers": {
"cloudbase-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cloudbase/cloudbase-mcp"
]
}
}
}VS Code CLI에 CloudBase MCP 설치
$ code --add-mcp '{"name":"cloudbase-mcp","type":"stdio","command":"npx","args":["-y","@cloudbase/cloudbase-mcp"]}'Claude Desktop에 CloudBase MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"cloudbase-mcp": {
"command": "npx",
"args": [
"-y",
"@cloudbase/cloudbase-mcp"
]
}
}
}Codex에 CloudBase MCP 설치
$ codex mcp add cloudbase-mcp -- npx -y @cloudbase/cloudbase-mcpCodex config.toml에 CloudBase MCP 설치
~/.codex/config.toml
[mcp_servers.cloudbase-mcp] command = "npx" args = ["-y", "@cloudbase/cloudbase-mcp"]
Gemini CLI에 CloudBase MCP 설치
$ gemini mcp add -s user cloudbase-mcp npx -- -y @cloudbase/cloudbase-mcpGemini settings.json에 CloudBase MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"cloudbase-mcp": {
"command": "npx",
"args": [
"-y",
"@cloudbase/cloudbase-mcp"
]
}
}
}자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기@cloudbase/cloudbase-mcp
MCP Server for Tencent CloudBase. Part of CloudBase AI Toolkit.
Operate CloudBase from AI coding tools: login, databases, functions, storage, hosting, and logs—via the Model Context Protocol.
English · 简体中文 · Toolkit README · Docs · Changelog · Issues
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": ["-y", "@cloudbase/npm-launcher@1.0.0", "@cloudbase/cloudbase-mcp@latest"]
}
}
}
First prompts:
Login to CloudBase
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 |
| Marketplace / built-in plugin | Claude Code, Codex, CodeBuddy, WorkBuddy, Doubao, MiniMax Code, DeepSeek Harness, Kimi Code, Kimi Work, ZCode, etc. |
Already using CloudBase CLI?
tcb aisets up MCP and Skills too (docs).
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.
OAuth (interactive, recommended): the URL is the whole configuration—your IDE opens the browser for login and consent, and you pick the environment there. No keys land in config files, and there is nothing to rotate.
{
"mcpServers": {
"cloudbase": {
"type": "http",
"url": "https://tcb-api.cloud.tencent.com/mcp/v1"
}
}
}
Static credentials (for a client without OAuth, and for CI/CD): append env_id and a key pair created on the same site as the endpoint.
{
"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>"
}
}
}
}
A static key pair stays valid until it is rotated or deleted; an OAuth session ends when you log out. Use the static form only where the browser flow is impossible—and keep it out of a repository.
Local: runs npx -y @cloudbase/npm-launcher@1.0.0 @cloudbase/cloudbase-mcp@latest on your machine—full features, including local filesystem upload and template download. Requires Node.js v18.15.0+.
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, feedback).
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.
MCP Apps panels (on by default)
auth, queryEnv and the deploy tools can render MCP Apps panels (ui://cloudbase/*) in hosts that support them. Panels are on by default: the ui:// resources are registered and those tools carry _meta.ui.
Hosts that cannot render them are unaffected in practice — resources/list stays empty (the panels are ResourceTemplates without a list), so nothing new appears in a resource browser, and every tool keeps returning the same JSON text it did before. The flag only decides whether panels are offered.
Turn it off with CLOUDBASE_MCP_UI=off (also accepts 0 / false / no / disabled). Leaving it unset means on; a typo such as of also leaves it off, so a misspelled value never silently enables something you meant to disable. Tools behave identically either way.
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
Confirmations before destructive calls
Deleting a cloud function, a collection, the documents in one, a stored file, a CloudRun service or a MySQL instance now pauses
the call until you answer a dialog that names the target — "about to delete the cloud function hello (env env-abc)" — instead
of asking a bare "are you sure?". The same deletes pause when they arrive as callCloudApi, but only for an explicit
service + Action pair: DeleteFunction on tcb or scf, tcb.DeleteTable, tcb.DeleteItem, tcb.DestroyEnv, tcb.DestroyPlatformEnv, tcb.DestroyMySQL,
tcbr.DeleteCloudRunServer, and tcbr.DeleteCloudRunVersions when IsDeleteServer is true. A Delete prefix does not
confirm other cloud APIs. Cloud storage deletes do not go through callCloudApi. PostgreSQL execute / applyMigration pause only when the SQL itself is DELETE, DROP, TRUNCATE or ALTER … DROP; INSERT, UPDATE and CREATE TABLE do not. It is built on MCP form elicitation, so it
can only appear where the client declares that capability and actually asks the user.
| Situation | What happens |
|---|---|
| The client asks the user | You get the dialog; the call runs only after you pick "delete" |
| The client is in a full-access / never-ask mode | It answers on its own within a few milliseconds. That is treated as "you were not asked", and the call proceeds |
| The client cannot render forms | No dialog, and the call proceeds — the behaviour is the same as before this change |
| You decline, dismiss it, or answer nothing for 45s | Nothing is executed, and the result says so without being marked as an error, so a model does not retry the same deletion |
A declined call is not a failure: the tool returns "not executed" plus what to do instead. Two environment variables change the handling, and neither of them bypasses authentication, permissions or read-only limits — they only decide whether the question is asked:
| Variable | Effect |
|---|---|
CLOUDBASE_MCP_SKIP_ELICITATIONS |
Comma-separated. Accepts a tool name (manageFunctions, callCloudApi) or a single action (manageFunctions.deleteFunction, callCloudApi.tcb.DeleteFunction), case-sensitive, no wildcard. Unknown entries are logged and ignored rather than failing the server |
CLOUDBASE_MCP_ELICIT_AUTO_APPROVE |
allow (default) proceeds when the client answers for itself; block treats that case as not confirmed |
A client's own tool-approval prompt is not this confirmation: it asks "may this tool run?", not "is this the resource you want to delete?".
Credential-shaped arguments: one real check before writing
When a call's arguments contain something shaped like a credential — a three-part JWT, or a cb_secret_… / cb_publishable_…
key — the server asks the client for one check before writing: compare the value against your original source and confirm. The
message deliberately carries no plaintext: only the total length, the segment lengths (for a JWT), and a fingerprint (the first
12 hex characters of sha256). That is enough to notice a value that was changed while being copied or transcribed, and nothing that
would put the secret into the conversation or into the logs.
What this is not. We do not decide whether the credential is valid. There is no signature verification, no certs/JWKS lookup,
no network request of any kind, and no server-side comparison — the server never sees the value you originally pasted, so the only
side that can compare it is the client. This is a request for a real confirmation at write time, not a validity check.
Boundaries. It only applies when the arguments actually contain a credential-shaped string (otherwise the call is unchanged: one shallow scan, no network). It only applies when the client supports interactive form elicitation; a client that cannot ask proceeds as before, so an unattended client is not blocked. And a check that returns within a few hundred milliseconds counts as "nobody looked at it": unlike the deletion confirmation — where a client answering for itself is treated as "you were not asked" and the call proceeds — a credential write is not executed, because a value nobody compared is exactly the case this guards against. When the guard declines, the result says "not executed" without being marked as an error, so a model does not retry it blindly.
| Variable | Effect |
|---|---|
CLOUDBASE_MCP_SKIP_CREDENTIAL_GUARD |
Comma-separated. Accepts a tool name (manageCloudRun) or a single action (manageCloudRun.updateConfig), case-sensitive, no wildcard. Unknown entries are logged and ignored rather than failing the server |
Environment panel (MCP Apps)
The panel is on by default. Set CLOUDBASE_MCP_UI=off to hide it. Where the client declares the io.modelcontextprotocol/ui extension, auth also opens a panel
(ui://cloudbase/get-started). It consumes the structured result that this auth call already returned and shows
the connection status: region, scope, and the environment ID. Signed-out users get a sign-in action. When no environment is bound, clicking a row binds it.
The panel does not touch cloud resources, but it is not a read-only surface. It makes two kinds of calls:
auth(status)— read-only, fired by "Re-check".auth(set_env)— fired when you click an environment row. It only rebinds the local environment for this session (an environment-scoped API key still cannot reach another environment), but it changes which environment every subsequent tool call uses, so pick the row deliberately.
Every other action just hands a sentence to the conversation. A result that carries a credentials block
(for example auth(get_temp_credentials) with reveal) does not open "View raw response", so that fold
never shows the key.
Clients that do not render MCP Apps are unaffected: auth keeps the same title, description, arguments and
output, and resources/list stays empty, so nothing new appears in a resource browser.
IDE config snippets
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["-y", "@cloudbase/npm-launcher@1.0.0", "@cloudbase/cloudbase-mcp@latest"]
}
}
}
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["-y", "@cloudbase/npm-launcher@1.0.0", "@cloudbase/cloudbase-mcp@latest"]
}
}
}
CloudBase is built in; manual MCP config is usually unnecessary.
Others: IDE setup.
Docs
License
CloudBase MCP 질문
CloudBase MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add cloudbase-mcp -- npx -y @cloudbase/cloudbase-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
CloudBase MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
CloudBase MCP server를 어떻게 설치하나요?
npx를 사용하여 다음 명령어로 설치할 수 있습니다: npx -y @cloudbase/npm-launcher@1.0.0 @cloudbase/cloudbase-mcp@latest.
서버에서 파괴적인 작업에 대한 보안을 제공하나요?
네, 함수나 데이터베이스 삭제와 같은 파괴적인 호출 시 대화 상자를 통해 확인을 요청하며 작업을 일시 중단합니다.
CloudBase MCP를 CI/CD에 사용할 수 있나요?
네, 자동화 및 CI/CD 목적을 위해 정적 자격 증명을 사용하는 Remote mode를 사용할 수 있습니다.