Cloudforge vs Terraform MCP Server
A side-by-side look at the Cloudforge and Terraform MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloudforge for cloud platforms work as a local process; choose Terraform MCP Server for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloudforge when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cloudforge_diagram_to_mermaid, cloudforge_architecture_summary, cloudforge_mermaid_from_json.
Choose Terraform MCP Server when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 55/100 · Good | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 1,553 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 50 | Not listed |
| Full listing | View Cloudforge | View Terraform MCP Server |
Tools & capabilities
Cloudforge tools 50
cloudforge_diagram_to_mermaidFetch a saved diagram and render it as an inline Mermaid flowchartcloudforge_architecture_summaryStructured summary: resource counts by category, central components, inline diagramcloudforge_mermaid_from_jsonConvert raw diagram JSON to Mermaid without fetching from the servercloudforge_generate_terraformGenerate Terraform HCL from a natural-language architecture descriptioncloudforge_export_terraform_from_diagramExport Terraform HCL from an existing saved diagram in one stepcloudforge_parse_terraformTurn raw HCL into a diagram structure — deterministic, no AI, **and no account neededcloudforge_export_terraformExport a saved diagram's Terraform as it stands, without regeneratingcloudforge_import_terraformParse existing HCL → diagram structure + Mermaid previewcloudforge_chatAsk the CloudForge AI Architect for IaC advice, cost estimates, security reviewscloudforge_suggest_resourcesGet AI-recommended resources and connections for a described use casecloudforge_list_moldsBrowse 90 curated architecture templates (30 per cloud) — filter by provider, category, or searchcloudforge_get_moldFull detail for one Mold: layout, "why this shape" best practices, inline Mermaid preview, forge link- +38 more on the listing page
Terraform MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cloudforge
{
"mcpServers": {
"cloudforge": {
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
]
}
}
}
Terraform MCP Server
{
"mcpServers": {
"hashicorp-terraform-mcp-server": {
"url": "http://localhost:8080/mcp"
}
}
}
Frequently asked questions
Cloudforge is categorized under Cloud Platforms and uses a local stdio subprocess. Terraform MCP Server belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Cloudforge for cloud platforms work and Terraform MCP Server for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cloudforge has no declared pricing — check the project's own site. Terraform MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cloudforge and hashicorp-terraform-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudforge has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Terraform MCP Server has 79/100 (Great) with 3 views, 0 installs and 1,553 GitHub stars.