Cloudforge
Diagram cloud architectures, generate Terraform HCL, and drive Azure, AWS, or GCP changes from your agent with a CloudForge API key.
Overview
CloudForge is a MCP server for the Build phase that visualizes cloud diagrams, generates Terraform HCL, and manages Azure, AWS, and GCP infrastructure through CloudForge.
What is this MCP server?
- Architecture visualization and Terraform HCL generation from AI-driven workflows
- Multi-cloud scope: Azure, AWS, and GCP management via CloudForge
- npm package cloudforge-mcp with stdio transport (registry v1.0.1)
- Requires CLOUDFORGE_TOKEN API key (cf_live_ prefix) from cloudforge.cloud/account
- Bridges diagram-first design to executable infrastructure definitions
- Version 1.0.1
- npm identifier: cloudforge-mcp
What problem does it solve?
Solo builders waste cycles translating architecture sketches into correct Terraform and juggling three cloud consoles without an agent-safe integration.
Who is it for?
Indie SaaS founders standardizing on Terraform who want AI-assisted diagrams and multi-cloud changes from Claude Code or Cursor.
Skip if: Teams avoiding third-party cloud control planes, air-gapped environments without API access, or pure on-prem bare-metal shops.
What do I get? / Deliverables
After you install cloudforge-mcp and set CLOUDFORGE_TOKEN, your agent can produce diagrams, HCL, and cloud management actions through CloudForge’s API.
- Cloud architecture diagrams produced via CloudForge from agent sessions
- Terraform HCL snippets or modules aligned to diagrammed resources
- Agent-mediated cloud resource management hooks for Azure, AWS, and GCP through CloudForge
Recommended MCP Servers
Journey fit
Infrastructure design and IaC generation happen while you integrate cloud services into the product you are building. Integrations is the canonical shelf for MCP servers that connect agents to third-party cloud control planes and Terraform workflows.
How it compares
CloudForge-backed IaC and diagram MCP, not a local-only tofu/terraform CLI wrapper skill.
Common Questions / FAQ
Who is CloudForge MCP for?
It is for builders using CloudForge who want MCP agents to diagram architectures, emit Terraform HCL, and interact with Azure, AWS, or GCP.
When should I use CloudForge MCP?
Use it while integrating cloud infrastructure during builds, or when iterating Terraform after the initial architecture is defined.
How do I add CloudForge MCP to my agent?
Install the npm package cloudforge-mcp, set CLOUDFORGE_TOKEN to a cf_live_ API key from cloudforge.cloud/account, and register the stdio server in your MCP client.