
Cloudcraft MCP
io.github.hypark5540Published by GitHub account hypark5540v0.1.8Updated Oct 26, 2026
Unofficial MCP server for reading and managing Cloudcraft architecture blueprints
Overview
Unofficial MCP server for Cloudcraft that lets an assistant list, read, export, create, update and delete cloud architecture blueprints.
- What you can do
- Check the Cloudcraft user profile behind the configured key
- List, read and inspect blueprints, teams, and connected AWS and Azure accounts
- Create, replace or delete blueprints from full JSON payloads
- Export blueprints as PNG, SVG, PDF or mxgraph images, and cost estimates as CSV or XLSX
- Live-scan one AWS or Azure region into blueprint JSON, with optional filter and exclude
- When to use it
- Useful when you keep cloud architecture diagrams in Cloudcraft and want an assistant to summarize existing blueprints, export diagrams or budget estimates, generate new blueprints from a design, or snapshot a connected cloud account region.
- Requirements
- Runs locally over stdio via uvx, pipx, npx, Docker or a Claude Desktop bundle; the npm launcher needs Node.js 22+ and uv. Requires a Cloudcraft API key in CLOUDCRAFT_API_KEY and network access to the Cloudcraft API; optional variables set the base URL, export directory, log level, response size limit, and write/delete gates.
Installation
In SourceWeft
- Open Cloudcraft MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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:
Requirements
- uv for the
recommended
uvxand 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.
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:
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.
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
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-2of 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:
Refer to Cloudcraft's API docs for the full node-type catalog and service-specific fields.
Development
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:
Project layout
Design notes
- Transport / logic split.
client.pyis a plain async HTTP client you can import from scripts or CLI tools without pulling the MCP runtime.server.pyonly owns the MCP tool surface. - Bearer-token auth. Cloudcraft's API expects
Authorization: Bearer <key>(notApikey). 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
CloudcraftErrorwith status and body preserved, re-wrapped asRuntimeErrorat 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=trueonly for clients that need create/update access. Deletes additionally requireCLOUDCRAFT_ENABLE_DELETES=trueand an exact repeated blueprint ID on every call. delete_blueprintis irreversible — when asking Claude to delete, be explicit about the target id.export_blueprint_imagewrites are sandboxed underCLOUDCRAFT_EXPORT_DIR(a process-private temporary subdirectory by default) and refuse to overwrite existing files unlessoverwrite=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
- Cloudcraft API documentation
- Model Context Protocol specification
- awslabs/mcp — AWS's collection of MCP servers
- modelcontextprotocol/servers — reference MCP server implementations
Source: README.md at commit 25ba3ab
Tools
0Version history
3- v0.1.8LatestOct 20, 2026
- v0.1.7Oct 8, 2026
- v0.1.6Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts