
Cloudinfra
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Terraform Registry docs, module search and AWS plan policy scans as MCP tools.
Overview
Cloudinfra's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Cloudinfra 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
cloudinfra
AWS infrastructure-as-code guidance as MCP tools: Terraform Registry documentation and module lookups, a local policy scan for terraform plan files, and plain-language explanations of common AWS resource types. cloudinfra is a clean-room rebuild of the core surface of the aws-terraform MCP server, under a new name: fresh code and prose, no copied branding.
Tools (core subset, 10)
search_provider_docs, get_provider_doc_details,
search_cc_provider_docs, list_provider_resources, search_modules,
get_module_details, get_latest_provider_version,
search_user_guide, run_policy_scan, explain_resource.
Not in this subset: Terraform/Tofu CLI execution (init/plan/apply), provider schema generation, pricing and cost estimation, LLM-assisted code or module generation, state manipulation, and any write or deploy operation.
How it works
The docs and module tools are shaped GET requests against the public
Terraform Registry API (https://registry.terraform.io/v1, base
overridable with TERRAFORM_REGISTRY_URL) through an injectable fetch
function. No credentials are needed for any tool.
run_policy_scan is fully local and deterministic. Give it a
terraform plan JSON (the output of terraform show -json) and it
walks planned_values (including child modules; resource_changes
is a fallback) checking four rule families:
public-s3— S3 buckets with a public ACLunencrypted-storage— RDS/EBS without encryption, S3 buckets with no server-side encryption configurationwildcard-iam— IAM policies granting wildcard actions or resourcesopen-security-group— ingress open to0.0.0.0/0or::/0
An external scanner can be injected through the library API as a scan executor; none is bundled — the local checker is the default and the only implemented scanner.
explain_resource answers from a small curated catalogue of common
AWS resource types written for this rebuild, and says so plainly for
types outside the catalogue.
CLI
Each tool name is a subcommand taking one JSON object argument.
MCP client config
Docker
Development
License
MIT
Source: README.md at commit a81f9c9
Tools
0Version history
1- v0.1.0LatestNov 3, 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