A Model Context Protocol (MCP) server for LocalStack that enables management of local AWS development environments, including container lifecycle operations, infrastructure deployments, log analysis with IAM policy generation, chaos injection, and Cloud Pods state management.
7
425 npm
29
Apache 2.0
Why this server?
Routes requests to the Terraform MCP server's tools for infrastructure-as-code providers, modules, and registry lookups when IaC assistance is needed.
Enables agents to connect through a single gateway that has a decision model pick which MCP tools and playbooks are relevant to each request, so the LLM only sees the few schemas it needs, and to then invoke those tools on the underlying servers. This cuts tool-selection cost and prompt size dramatically when many MCP servers are connected.
2
4
MIT
Why this server?
Allows guarding of Terraform commands (e.g., terraform destroy) by blocking dangerous infrastructure operations until human approval.
A cooperative guardrail for AI agents that blocks destructive shell commands, SQL statements, or cloud operations until a human approves them out-of-band, with a tamper-evident local ledger.
4
AGPL 3.0
Why this server?
Integrates with Terraform Cloud API, enabling workspace management (create, read, update, delete, lock/unlock) and authentication capabilities
A Model Context Protocol (MCP) server that integrates Claude with the Terraform Cloud API, allowing Claude to manage your Terraform infrastructure through natural conversation.
62
23
MIT
Why this server?
Analyzes Terraform configurations for multi-hop attack paths from the public internet to crown jewels, such as data stores and secrets.
MCP server for auditing infrastructure-as-code attack paths, finding multi-hop chains from public internet to sensitive resources.
2
MIT
Why this server?
Prices Terraform plans using your actual AWS rates, evaluates the cost impact of infrastructure changes, and can generate mergeable fixes for cost findings in your working copy.
Enables analyzing AWS cloud costs from billing data, identifying waste, and providing mergeable fixes, with findings reconciled to actual invoices and priced at your negotiated rates.
6
35 PyPI
MIT
Why this server?
Enables running Terraform commands with injected cloud credentials, enforcing policies and masking secrets.
Enables AI agents to make authenticated API calls and run commands with secrets injected, while keeping credentials completely hidden from the model, with policy enforcement, grants, and audit logging.
6
MIT
Why this server?
Scans Terraform configurations for security misconfigurations, explains findings, applies safe fixes, provides hardened templates, and maps results to compliance frameworks.
Enables local-first scanning of Terraform for security misconfigurations while an AI assistant writes the code, providing fixes and compliance mappings without uploading infrastructure code.
8
7
Apache 2.0
Why this server?
Enables security scanning of Terraform plan JSON, generating per-resource findings with severity, remediation guidance, and citations grounded in CIS AWS Foundations and OWASP Top 10 CI/CD Security Risks.
Enables AI coding agents to search a security corpus, scan Terraform plan JSON for cited findings, and list sources via MCP tools grounded in CIS AWS Foundations and OWASP Top 10 CI/CD risks.
