Visualise diagrams, generate Terraform HCL, and manage Azure/AWS/GCP infrastructure with AI.
Visualise diagrams, generate Terraform HCL, and manage Azure/AWS/GCP infrastructure with AI. That is what the cloudforge mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP server for CloudForge — lets Claude and other AI assistants visualise cloud architecture diagrams, generate Terraform HCL, import existing IaC, and manage your infrastructure resources directly from chat.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 3 tools. What each one is for:
Visualisation — The Visualisation tool exposed by this serverTerraform — The Terraform tool exposed by this serverOrganisation — The Organisation tool exposed by this serverConfiguration is passed through the environment: CLOUDFORGE_TOKEN, CLOUDFORGE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cloudforge's toolset — Visualisation, Terraform, Organisation — is a fair guide to whether it matches your workflow. It is maintained by cloudforgetech6-ctrl; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Visualisation | The Visualisation tool exposed by this server. |
| Terraform | The Terraform tool exposed by this server. |
| Organisation | The Organisation tool exposed by this server. |
{
"mcpServers": {
"cloudforge": {
"command": "npx",
"args": ["-y", "cloudforge-mcp"],
"env": {
"CLOUDFORGE_TOKEN": "your-bearer-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CLOUDFORGE_TOKEN | Credential the server authenticates with. | Yes |
| CLOUDFORGE_API_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.