MCP servers · cloudcorprecords

cloudinfra: AWS infrastructure-as-code tools for MCP clients

An MCP server offering Terraform Registry documentation and module lookups, a local policy scan of Terraform plan files, and plain-language explanations of common AWS resource types.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

cloudinfra provides ten MCP tools for AWS infrastructure-as-code work. They search and read Terraform Registry provider documentation and modules, explain common AWS resource types in plain language, and run a local policy scan on Terraform plan files. It is a clean-room rebuild of the core of the aws-terraform MCP server.

Use it when you need to look up provider resources or module details from the Terraform Registry, or when you want to check a plan for public S3 buckets, unencrypted RDS, EBS or S3 storage, IAM policies with wildcard actions or resources, or security group ingress open to 0.0.0.0/0 or ::/0.

The registry tools send GET requests to the public Terraform Registry API, and no credentials are needed for any tool. The policy scan runs entirely locally and deterministically. It takes the JSON output of a Terraform plan, walks planned_values including child modules, and falls back to resource_changes. Each tool is also available as a CLI subcommand that takes a single JSON object argument, and it can be configured in an MCP client.

Limitations and requirements

Terraform and OpenTofu 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 are not included. The policy scan needs a Terraform plan JSON as input. The local checker is the only implemented scanner; external scanners must be injected through the library API and none is bundled. explain_resource covers only a small curated catalogue of AWS resource types and states so plainly for types outside it.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/cloudinfra

    Terraform Registry docs, module search and AWS plan policy scans as MCP tools.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026