Permite que assistentes de IA visualizem arquitetura de nuvem, gerem Terraform HCL e gerenciem infraestrutura AWS, Azure e GCP via chat.
Também conhecido como cloudforgetech6-ctrl/mcp_server, mcp-server, cloudforge-mcp
- Stars
- 0
- Ferramentas
- 50
- Downloads, 30 dias
- —
- Versão mais recente
- 1.1.0
- Último commit
- 13 de out. de 2026
- Licença
- MIT
O que é o MCP CloudForge?
CloudForge é um MCP server. Permite que assistentes de IA visualizem arquitetura de nuvem, gerem Terraform HCL e gerenciem infraestrutura AWS, Azure e GCP via chat. Ele expõe 50 ferramentas, como cloudforge_diagram_to_mermaid, cloudforge_architecture_summary, cloudforge_mermaid_from_json.
Resumo gerado a partir do README do projeto
Sobre o MCP server de CloudForge
O CloudForge fornece uma interface para assistentes de IA gerenciarem infraestrutura de nuvem em AWS, Azure e GCP. Desenvolvedores podem usar este servidor para visualizar arquitetura por meio de diagramas Mermaid, gerar Terraform HCL a partir de linguagem natural e importar código existente para estruturas visuais. Ele preenche a lacuna entre o planejamento via chat e a implantação no mundo real, oferecendo ferramentas para estimativa de custos, revisões de segurança e detecção de drift.
Os usuários se conectam via um bearer token começando com cf_live_ configurado em suas configurações de MCP. O servidor suporta ambientes locais e self-hosted através do ajuste da URL da API. Para garantir a segurança durante mudanças de infraestrutura, o sistema inclui um gate de aprovação humana obrigatório para todas as operações de apply e destroy. Isso evita que um agente de IA realize modificações não autorizadas ou acidentais em recursos de nuvem ativos sem consentimento explícito através da ferramenta cloudforge_approve_deployment.
O que você pode fazer com ele
- 1Converter HCL em diagramasTransforme código Terraform bruto em uma estrutura de diagrama visual para facilitar o entendimento.
- 2Gerar infraestrutura a partir de descriçõesCrie arquivos Terraform HCL baseados em uma descrição em linguagem natural de uma arquitetura desejada.
- 3Auditar drift de nuvem e conformidadeCompare os recursos atualmente implantados com diagramas salvos e realize varreduras contra frameworks de segurança.
- 4Revisar arquitetura para custo e segurançaPeça a um arquiteto de IA para avaliar um design quanto à confiabilidade, segurança e possíveis trade-offs de escalabilidade.
Escrito a partir do README do projeto. Cada caso de uso é verificado com uma citação dele.
Como instalar o MCP CloudForge
Formatos verificados em 10 nov 2026Adicionar ao CursorAdicionar ao GooseInstalar o MCP CloudForge no Claude Code
$ claude mcp add --env 'CLOUDFORGE_TOKEN=<YOUR_CLOUDFORGE_TOKEN>' mcp-server -- npx -y cloudforge-mcpInstalar o MCP CloudForge no Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
],
"env": {
"CLOUDFORGE_TOKEN": "<YOUR_CLOUDFORGE_TOKEN>"
}
}
}
}Instalar o MCP CloudForge no VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
],
"env": {
"CLOUDFORGE_TOKEN": "<YOUR_CLOUDFORGE_TOKEN>"
}
}
}
}Instalar o MCP CloudForge no VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","cloudforge-mcp"],"env":{"CLOUDFORGE_TOKEN":"<YOUR_CLOUDFORGE_TOKEN>"}}'Instalar o MCP CloudForge no Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
],
"env": {
"CLOUDFORGE_TOKEN": "<YOUR_CLOUDFORGE_TOKEN>"
}
}
}
}Instalar o MCP CloudForge no Codex
$ codex mcp add mcp-server --env 'CLOUDFORGE_TOKEN=<YOUR_CLOUDFORGE_TOKEN>' -- npx -y cloudforge-mcpInstalar o MCP CloudForge no Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "cloudforge-mcp"] [mcp_servers.mcp-server.env] CLOUDFORGE_TOKEN = "<YOUR_CLOUDFORGE_TOKEN>"
Instalar o MCP CloudForge no Gemini CLI
$ gemini mcp add -s user -e 'CLOUDFORGE_TOKEN=<YOUR_CLOUDFORGE_TOKEN>' mcp-server npx -- -y cloudforge-mcpInstalar o MCP CloudForge no Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
],
"env": {
"CLOUDFORGE_TOKEN": "<YOUR_CLOUDFORGE_TOKEN>"
}
}
}
}Ferramentas do MCP CloudForge 50
Detectadas a partir do READMEcloudforge_diagram_to_mermaidcloudforge_architecture_summarycloudforge_mermaid_from_jsoncloudforge_generate_terraformcloudforge_export_terraform_from_diagramcloudforge_parse_terraformcloudforge_export_terraformcloudforge_import_terraformcloudforge_chatcloudforge_suggest_resourcescloudforge_list_moldscloudforge_get_mold
| cloudforge_diagram_to_mermaid | — | |
| cloudforge_architecture_summary | — | |
| cloudforge_mermaid_from_json | — | |
| cloudforge_generate_terraform | — | |
| cloudforge_export_terraform_from_diagram | — | |
| cloudforge_parse_terraform | — | |
| cloudforge_export_terraform | — | |
| cloudforge_import_terraform | — | |
| cloudforge_chat | — | |
| cloudforge_suggest_resources | — | |
| cloudforge_list_molds | — | |
| cloudforge_get_mold | — |
Mostrar todas as 50 ferramentasMostrar menos ferramentas
cloudforge_list_diagramscloudforge_recent_diagramscloudforge_get_diagramcloudforge_save_diagramcloudforge_delete_diagramcloudforge_org_detailscloudforge_list_memberscloudforge_invite_membercloudforge_list_invitationscloudforge_cancel_invitationcloudforge_remove_membercloudforge_get_pricingcloudforge_plancloudforge_dry_runcloudforge_validate_deploymentcloudforge_applycloudforge_destroycloudforge_approve_deploymentcloudforge_deployment_statuscloudforge_deployment_historycloudforge_fix_terraformcloudforge_validate_terraformcloudforge_estimate_costcloudforge_review_architecturecloudforge_scan_driftcloudforge_latest_driftcloudforge_drift_reportcloudforge_compliance_frameworkscloudforge_compliance_scancloudforge_detect_remediationscloudforge_list_remediationscloudforge_heal_approvedcloudforge_remediation_ledgercloudforge_remediation_policycloudforge_list_policiescloudforge_evaluate_policiescloudforge_foundry_diagramscloudforge_list_templates
| cloudforge_list_diagrams | — | |
| cloudforge_recent_diagrams | — | |
| cloudforge_get_diagram | — | |
| cloudforge_save_diagram | — | |
| cloudforge_delete_diagram | — | |
| cloudforge_org_details | — | |
| cloudforge_list_members | — | |
| cloudforge_invite_member | — | |
| cloudforge_list_invitations | — | |
| cloudforge_cancel_invitation | — | |
| cloudforge_remove_member | — | |
| cloudforge_get_pricing | — | |
| cloudforge_plan | — | |
| cloudforge_dry_run | — | |
| cloudforge_validate_deployment | — | |
| cloudforge_apply | — | |
| cloudforge_destroy | — | |
| cloudforge_approve_deployment | — | |
| cloudforge_deployment_status | — | |
| cloudforge_deployment_history | — | |
| cloudforge_fix_terraform | — | |
| cloudforge_validate_terraform | — | |
| cloudforge_estimate_cost | — | |
| cloudforge_review_architecture | — | |
| cloudforge_scan_drift | — | |
| cloudforge_latest_drift | — | |
| cloudforge_drift_report | — | |
| cloudforge_compliance_frameworks | — | |
| cloudforge_compliance_scan | — | |
| cloudforge_detect_remediations | — | |
| cloudforge_list_remediations | — | |
| cloudforge_heal_approved | — | |
| cloudforge_remediation_ledger | — | |
| cloudforge_remediation_policy | — | |
| cloudforge_list_policies | — | |
| cloudforge_evaluate_policies | — | |
| cloudforge_foundry_diagrams | — | |
| cloudforge_list_templates | — |
Configuração
CLOUDFORGE_TOKENObrigatórioSecretoCloudForge API key — generate one at cloudforge.cloud/account under API Keys. Must start with cf_live_
CLOUDFORGE_API_URL
| Nome | Descrição | Tipo |
|---|---|---|
| CLOUDFORGE_TOKEN | CloudForge API key — generate one at cloudforge.cloud/account under API Keys. Must start with cf_live_ | ObrigatórioSecreto |
| CLOUDFORGE_API_URL | — |
Verificações automatizadas
Executado em 13 de nov. de 2026Relatório completo →Passou em nossas verificações automatizadas. Isso não é uma auditoria de segurança: leia o código e dê ao servidor o acesso mais restrito de que ele precisa. Como as verificações funcionam
- Repositório de origem vinculado e acessívelPassou
- Licença de código aberto (OSI)Passou
- Commit ou release no último anoPassou
- Nome do pacote não é próximo a um pacote popularPassou
- O endpoint remoto usa HTTPSNão verificado
- Ferramentas destrutivas estão rotuladasPassou
- Sem instruções ocultas para o modeloPassou
- Nenhum aviso crítico no pacote ou em suas dependênciasPassou
README
Ver no GitHubCloudForge MCP Server
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.
Tools
Visualisation
| Tool | Description |
|---|---|
cloudforge_diagram_to_mermaid |
Fetch a saved diagram and render it as an inline Mermaid flowchart |
cloudforge_architecture_summary |
Structured summary: resource counts by category, central components, inline diagram |
cloudforge_mermaid_from_json |
Convert raw diagram JSON to Mermaid without fetching from the server |
Terraform
| Tool | Description |
|---|---|
cloudforge_generate_terraform |
Generate Terraform HCL from a natural-language architecture description |
cloudforge_export_terraform_from_diagram |
Export Terraform HCL from an existing saved diagram in one step |
cloudforge_parse_terraform |
Turn raw HCL into a diagram structure — deterministic, no AI, and no account needed |
cloudforge_export_terraform |
Export a saved diagram's Terraform as it stands, without regenerating |
cloudforge_import_terraform |
Parse existing HCL → diagram structure + Mermaid preview |
AI Architect
| Tool | Description |
|---|---|
cloudforge_chat |
Ask the CloudForge AI Architect for IaC advice, cost estimates, security reviews |
cloudforge_suggest_resources |
Get AI-recommended resources and connections for a described use case |
Mold Library
| Tool | Description |
|---|---|
cloudforge_list_molds |
Browse 90 curated architecture templates (30 per cloud) — filter by provider, category, or search |
cloudforge_get_mold |
Full detail for one Mold: layout, "why this shape" best practices, inline Mermaid preview, forge link |
Diagram Management
| Tool | Description |
|---|---|
cloudforge_list_diagrams |
List saved diagrams with metadata |
cloudforge_recent_diagrams |
Get recently accessed/modified diagrams |
cloudforge_get_diagram |
Fetch a diagram by ID (full JSON) |
cloudforge_save_diagram |
Save or update a diagram |
cloudforge_delete_diagram |
Permanently delete a diagram |
Organisation
| Tool | Description |
|---|---|
cloudforge_org_details |
Organisation overview: name, plan, member count, MFA policy, custom assistant name |
cloudforge_list_members |
List organisation members (name, email, role, status) |
cloudforge_invite_member |
Send an organisation invitation |
cloudforge_list_invitations |
List pending invitations |
cloudforge_cancel_invitation |
Cancel a pending invitation |
cloudforge_remove_member |
Remove a member from the organisation |
Pricing
| Tool | Description |
|---|---|
cloudforge_get_pricing |
Get CloudForge's current plans & pricing (Free, Pro, Team, Business), incl. the 14-day free trial — fetched live |
Deploy
Real infrastructure changes. apply and destroy stop at a human approval gate and change
nothing until cloudforge_approve_deployment is called, so an agent cannot deploy on its own.
| Tool | Description |
|---|---|
cloudforge_plan |
Run terraform plan — add/change/destroy diff plus the security quality gate. Read-only |
cloudforge_dry_run |
Validate and plan without touching a cloud account |
cloudforge_validate_deployment |
Provider and HCL pre-flight checks |
cloudforge_apply |
Start a real deployment. Creates resources and costs money; stops at the approval gate |
cloudforge_destroy |
Start a destroy. Permanently deletes infrastructure; same approval gate |
cloudforge_approve_deployment |
Approve or reject a job waiting at its gate — the step that actually changes the cloud |
cloudforge_deployment_status |
Status and log of one job |
cloudforge_deployment_history |
Every deployment run against a diagram |
Quality & cost
| Tool | Description |
|---|---|
cloudforge_fix_terraform |
Repair broken HCL from an error log — the same healer the deployment pipeline uses on itself |
cloudforge_validate_terraform |
Syntax and provider-schema check without deploying |
cloudforge_estimate_cost |
Estimated monthly cost, per resource |
cloudforge_review_architecture |
AI review: reliability, security, cost, scaling trade-offs |
Drift & compliance
| Tool | Description |
|---|---|
cloudforge_scan_drift |
Compare a diagram against what is actually deployed |
cloudforge_latest_drift |
Most recent drift report for a diagram |
cloudforge_drift_report |
Read one drift report by id — poll this after a scan |
cloudforge_compliance_frameworks |
Frameworks available to scan against (APRA CPS 234, CIS, …) |
cloudforge_compliance_scan |
Scan against frameworks — deterministic evidence and control mappings, never an AI opinion |
Self-healing — detect, approve, heal
Three steps, always in that order. There is deliberately no tool that approves a fix: approval means a person read what would change and consented to it, and a tool that let an assistant grant that consent on their behalf would remove the only guarantee the feature offers. Detect and report freely; the user approves in the CloudForge panel, the VS Code extension or the JetBrains tool window; then heal.
| Tool | Description |
|---|---|
cloudforge_detect_remediations |
Turn a completed drift report into proposed fixes, all awaiting a person's decision |
cloudforge_list_remediations |
Proposals and where each one stands |
cloudforge_heal_approved |
Apply only what a person approved; pauses at the Terraform plan for a second yes |
cloudforge_remediation_ledger |
The append-only audit trail: what changed, why, and who said it could |
cloudforge_remediation_policy |
The bounds healing works inside — excluded resource types, how long a proposal stays actionable |
Governance
| Tool | Description |
|---|---|
cloudforge_list_policies |
Governance policies configured for the organisation |
cloudforge_evaluate_policies |
Check a design against them before deploying — the pipeline enforces the same rules |
Shared work
| Tool | Description |
|---|---|
cloudforge_foundry_diagrams |
Diagrams shared across the organisation (The Foundry) |
cloudforge_list_templates |
Organisation-authored templates, distinct from the built-in Molds |
Setup
Claude Desktop (recommended)
Add to your claude_desktop_config.json:
{
"mcpServers": {
"cloudforge": {
"command": "npx",
"args": ["-y", "cloudforge-mcp"],
"env": {
"CLOUDFORGE_TOKEN": "your-bearer-token"
}
}
}
}
Claude Code / .mcp.json
{
"mcpServers": {
"cloudforge": {
"command": "npx",
"args": ["-y", "cloudforge-mcp"],
"env": {
"CLOUDFORGE_TOKEN": "your-bearer-token"
}
}
}
}
Authentication
- Sign in at cloudforge.cloud
- Go to Account → API Keys
- Click Generate API Key, give it a name (e.g.
CloudForge MCP), and copy the key — it starts withcf_live_and is shown only once - Set it as
CLOUDFORGE_TOKENin your MCP config
The key is long-lived and can be revoked from the same page at any time.
Environment Variables
| Variable | Default | Description |
|---|---|---|
CLOUDFORGE_TOKEN |
(required) | CloudForge API key — must start with cf_live_ |
CLOUDFORGE_API_URL |
https://cloudforge.cloud/api |
API base URL — only change if self-hosting |
Example prompts
Show me my recent diagrams
What serverless Molds do you have for AWS?
Show me the azure-3-tier-web-app Mold and explain why it's shaped that way
Render diagram <id> as a Mermaid chart
Generate Terraform for a 3-tier Azure web app with a private SQL database in UK South
Import this Terraform and show me a diagram: <paste HCL>
What are the security best practices for the resources in diagram <id>?
Invite john@example.com as a Member to my organisation
Pricing
The cloudforge_get_pricing tool returns CloudForge's current plans live (so they're always up to date). All prices USD; paid plans include a 14-day free trial:
| Plan | Price |
|---|---|
| Free | $0 — visual designer, limited export, community support |
| Pro | US$9.99/mo or US$99/yr · 14-day free trial |
| Team | US$12/user/mo (3-seat min) · 14-day free trial |
| Business | Contact us — volume/annual pricing |
Full details: cloudforge.cloud/pricing.
Self-hosting
If you run CloudForge on-premises, point the server at your own API:
"env": {
"CLOUDFORGE_API_URL": "https://your-cloudforge-host/api",
"CLOUDFORGE_TOKEN": "your-token"
}
License
MIT © CloudForge
Perguntas sobre o MCP CloudForge
Como adiciono o MCP CloudForge ao Claude Code?
Execute claude mcp add --env 'CLOUDFORGE_TOKEN=<YOUR_CLOUDFORGE_TOKEN>' mcp-server -- npx -y cloudforge-mcp no seu terminal. Adicione --scope user para torná-lo disponível em todos os projetos.
Como adiciono o MCP CloudForge ao Cursor?
Abra ~/.cursor/mcp.json e adicione o servidor em mcpServers, usando a configuração do Cursor mostrada na seção de instalação acima.
Quais ferramentas o MCP CloudForge oferece?
Ele expõe 50 ferramentas, incluindo cloudforge_diagram_to_mermaid, cloudforge_architecture_summary, cloudforge_mermaid_from_json, cloudforge_generate_terraform, cloudforge_export_terraform_from_diagram.
A IA pode implantar infraestrutura por conta própria?
Não, mudanças reais na infraestrutura exigem uma etapa de aprovação humana. O agente não pode implantar sozinho porque o processo para em um gate de aprovação até que um humano chame a ferramenta de aprovação.
Preciso de uma conta para converter Terraform HCL em um diagrama?
Não, a ferramenta que transforma HCL bruto em uma estrutura de diagrama é determinística e não requer uma conta.
Como faço a autenticação com o CloudForge MCP server?
Você deve gerar uma chave de API começando com cf_live_ nas configurações da sua conta CloudForge e defini-la como a variável de ambiente CLOUDFORGE_TOKEN.
O CloudForge oferece um período de teste gratuito?
Sim, os planos pagos incluem um teste gratuito de 14 dias.