Cloudcraft MCP

io.github.hypark5540由 GitHub 帳號 hypark5540 發布v0.1.8更新於 Oct 26, 2026

Unofficial MCP server for reading and managing Cloudcraft architecture blueprints

概覽

AI 產生的概覽

Cloudcraft 的非官方 MCP 伺服器,讓助理列出、讀取、匯出、建立、更新與刪除雲端架構藍圖。

可以做什麼
  • 查看目前金鑰對應的 Cloudcraft 使用者資料
  • 列出、讀取與檢視藍圖、團隊,以及已連線的 AWS 與 Azure 帳戶
  • 以完整 JSON 內容建立、取代或刪除藍圖
  • 將藍圖匯出為 PNG、SVG、PDF 或 mxgraph 圖片,並將成本估算匯出為 CSV 或 XLSX
  • 即時掃描某個 AWS 或 Azure 區域並產生藍圖 JSON,可選擇過濾與排除
適用情境
適合在 Cloudcraft 中維護雲端架構圖的情境:讓助理摘要現有藍圖、匯出架構圖或預算估算、依設計建立新藍圖,或對已連線的雲端帳戶區域做快照。
執行需求
透過 uvx、pipx、npx、Docker 或 Claude Desktop 安裝包在本機以 stdio 執行;npm 啟動方式需要 Node.js 22+ 與 uv。需要 Cloudcraft API 金鑰(環境變數 CLOUDCRAFT_API_KEY)以及連線 Cloudcraft API 的網路;選用變數可設定基礎 URL、匯出目錄、日誌等級、回應大小上限與寫入/刪除開關。
安裝前請注意
Cloudcraft API 金鑰擁有帳戶完整的讀寫權限,應視為機密並定期輪換。寫入預設關閉,刪除還須同時開啟 CLOUDCRAFT_ENABLE_WRITES 與 CLOUDCRAFT_ENABLE_DELETES,並在每次呼叫中重複精確的藍圖 ID;刪除無法復原。工具註解僅為提示,請保持主機端的工具核准功能開啟。匯出檔案會寫入 CLOUDCRAFT_EXPORT_DIR 指定的目錄。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Cloudcraft MCP,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

cloudcraft-mcp

[CI] [codecov] [PyPI] [npm] [License: MIT] [Python 3.10+]

Unofficial Model Context Protocol (MCP) server for Cloudcraft — list, read, export, and build cloud architecture blueprints from Claude Desktop and other MCP clients.

Features

Thirteen tools exposed to the MCP host:

ToolDescription
whoamiReturn the Cloudcraft user profile for the configured key.
list_blueprintsList every blueprint in the account.
get_blueprintFetch a blueprint's full node / edge JSON.
create_blueprintCreate a new blueprint from a JSON payload.
update_blueprintReplace an existing blueprint's payload.
delete_blueprintDelete a blueprint (irreversible).
export_blueprint_imageRender a blueprint to PNG / SVG / PDF / mxgraph on disk.
export_blueprint_budgetExport a blueprint's cost estimate as CSV / XLSX on disk.
list_teamsList teams linked to the account.
list_aws_accountsList AWS accounts connected for live-scan snapshots.
snapshot_awsLive-scan one AWS region into blueprint JSON (optional filter / exclude).
list_azure_accountsList Azure accounts connected for live-scan snapshots.
snapshot_azureLive-scan one Azure region into blueprint JSON (optional filter / exclude).

Requirements

  • uv for the recommended uvx and npm launchers
  • Node.js 22+ only when using the npm launcher
  • Cloudcraft API key — generate one at https://app.cloudcraft.co/ → User settings → API keys

Install

Use an immutable version in client configuration so upgrades are deliberate.

ChannelCommand
PyPI / uvxuvx --from cloudcraft-mcp==0.1.8 cloudcraft-mcp
pipxpipx run --spec cloudcraft-mcp==0.1.8 cloudcraft-mcp
npm / npxnpx -y @hypark5540/[email protected]
Docker / GHCRdocker run --rm -i -e CLOUDCRAFT_API_KEY ghcr.io/hypark5540/cloudcraft-mcp:0.1.8
Claude DesktopDownload cloudcraft-mcp.mcpb from the matching GitHub release

uvx is delivered by the PyPI package; there is no separate uvx registry. The npm package embeds the byte-identical Python wheel and invokes it through uv, so the npm path requires both Node.js and uv. It does not download code in a postinstall hook.

For development from a checkout:

bash
git clone https://github.com/hypark5540/cloudcraft-mcp.gitcd cloudcraft-mcpexport CLOUDCRAFT_API_KEY='your-key-here'uv run --frozen cloudcraft-mcp   # Ctrl+C to exit

Claude Desktop integration

Install uv, then add this entry to Claude Desktop's configuration. Prefer Claude's secret storage when available; the literal below is only a portable example.

json
{  "mcpServers": {    "cloudcraft": {      "command": "uv",      "args": [        "tool",        "run",        "--isolated",        "--from",        "cloudcraft-mcp==0.1.8",        "cloudcraft-mcp"      ],      "env": {        "CLOUDCRAFT_API_KEY": "your-key-here",        "CLOUDCRAFT_ENABLE_WRITES": "false",        "CLOUDCRAFT_ENABLE_DELETES": "false"      }    }  }}

Restart Claude Desktop. The Developer tab should show cloudcraft as connected.

See client setup for Cursor, Gemini CLI, npm, Docker, and MCPB examples.

Environment variables

NameRequiredDefaultPurpose
CLOUDCRAFT_API_KEYyes—API key (Bearer). Generated in Cloudcraft User settings.
CLOUDCRAFT_BASE_URLnohttps://api.cloudcraft.coOverride for proxies or future API versions.
CLOUDCRAFT_LOG_LEVELnoWARNINGStderr log verbosity (DEBUG / INFO / WARNING / ERROR).
CLOUDCRAFT_EXPORT_DIRnoprivate temp subdirectoryDirectory that export_blueprint_image may write under.
CLOUDCRAFT_ENABLE_WRITESnofalsePermit create_blueprint and update_blueprint.
CLOUDCRAFT_ENABLE_DELETESnofalsePermit deletes when writes are also enabled.
CLOUDCRAFT_MAX_RESPONSE_BYTESno26214400Reject oversized Cloudcraft responses before they exhaust memory or disk.

Usage examples (in Claude)

Once the server is connected, ask Claude things like:

"List my Cloudcraft blueprints and summarize what each represents."

"Export blueprint f0086b32-... as PNG and save it to my Desktop."

"Take the architecture I just designed and create a new Cloudcraft blueprint called 'Prod 2026'."

"Snapshot ap-northeast-2 of my connected AWS account, excluding security groups."

"Export the monthly budget of blueprint f0086b32-... as CSV in EUR."

Blueprint payload shape

create_blueprint / update_blueprint accept the full Cloudcraft data object. A minimal payload:

json
{  "grid": "infinite",  "projection": "isometric",  "theme": {"base": "light"},  "version": 6,  "nodes": [    {"id": "...", "type": "ec2", "mapPos": [3, 3], "region": "ap-northeast-2",     "instanceType": "m7g", "instanceSize": "large", "platform": "linux"},    {"id": "...", "type": "s3",  "mapPos": [1, 8], "region": "ap-northeast-2",     "volumeType": "Standard", "dataGb": 100}  ],  "edges": [    {"from": "...ec2-id...", "to": "...s3-id...", "type": "edge",     "width": 2, "dashed": false, "endCap": "arrow"}  ],  "groups": [], "surfaces": [], "text": [], "icons": [],  "connectors": [], "images": [], "disabledLayers": [],  "shareDocs": false}

Refer to Cloudcraft's API docs for the full node-type catalog and service-specific fields.

Development

bash
uv sync --extra devuv run pytest            # unit tests (no network)uv run ruff check .      # lintuv run mypy src          # type check

Tests mock the HTTP layer with respx so no API key is required.

Coverage

CI uploads coverage.xml from the Python 3.12 matrix cell to Codecov. The project gate is 80% or higher — a PR that drops overall or patch coverage by more than 1 percentage point below that line fails the Codecov check (codecov.yml).

Run the same report locally:

bash
uv run pytest --cov=cloudcraft_mcp --cov-report=term-missing --cov-report=xml

Project layout

cloudcraft-mcp/├── src/cloudcraft_mcp/│   ├── __init__.py│   ├── __main__.py         # python -m cloudcraft_mcp│   ├── server.py           # MCP tool definitions (FastMCP)│   ├── client.py           # CloudcraftClient — async httpx wrapper│   ├── types.py            # TypedDicts for blueprint payloads│   └── py.typed├── tests/│   └── test_client.py├── bin/cloudcraft-mcp.mjs # npm-to-uv launcher├── mcpb/manifest.json     # Claude Desktop bundle metadata├── server.json            # official MCP Registry metadata├── package.json           # npm distribution├── server.py               # back-compat shim -> cloudcraft_mcp.server:main├── pyproject.toml├── LICENSE└── README.md

Design notes

  • Transport / logic split. client.py is a plain async HTTP client you can import from scripts or CLI tools without pulling the MCP runtime. server.py only owns the MCP tool surface.
  • Bearer-token auth. Cloudcraft's API expects Authorization: Bearer <key> (not Apikey). The client sets this automatically.
  • No secrets in process args. The API key is read from CLOUDCRAFT_API_KEY; never pass it on the command line.
  • One implementation. PyPI, npm, MCPB, and the container all launch the same versioned Python package rather than maintaining language-specific forks.
  • Error surface. Non-2xx responses raise CloudcraftError with status and body preserved, re-wrapped as RuntimeError at the MCP boundary so Claude sees a readable message.

Security

  • API keys grant full read / write over your Cloudcraft account. Treat them as secrets and rotate regularly.
  • MCP tool annotations mark read-only tools and mutating/destructive tools so compatible hosts can present better approval prompts. These annotations are hints, not an enforcement layer.
  • Environment gates and exact-ID delete confirmation are defense in depth, not an interactive approval workflow; keep the MCP host's tool approval UX enabled.
  • Cloudcraft mutations are disabled by default. Set CLOUDCRAFT_ENABLE_WRITES=true only for clients that need create/update access. Deletes additionally require CLOUDCRAFT_ENABLE_DELETES=true and an exact repeated blueprint ID on every call.
  • delete_blueprint is irreversible — when asking Claude to delete, be explicit about the target id.
  • export_blueprint_image writes are sandboxed under CLOUDCRAFT_EXPORT_DIR (a process-private temporary subdirectory by default) and refuse to overwrite existing files unless overwrite=True.
  • For read-heavy setups, create a dedicated Cloudcraft user with read-only scope (if/when Cloudcraft adds scoped keys) and use that key for MCP.
  • Supported versions and private reporting instructions are in SECURITY.md; data flow is documented in PRIVACY.md.

Contributing

Issues and PRs welcome at https://github.com/hypark5540/cloudcraft-mcp. Please run ruff, mypy, and pytest before submitting.

License

MIT — see LICENSE.

Related

來源:README.md,提交 25ba3ab

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

3
  1. v0.1.8最新Oct 20, 2026
  2. v0.1.7Oct 8, 2026
  3. v0.1.6Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分