"A platform for managing infrastructure as code with Terraform Cloud" matching MCP servers:

Enables Terraform HCL plan generation, drift detection, and strict human confirmation approval barriers for cloud infrastructure management.

Enables coding agents to add a bounded semantic-judgment layer for routing, ranking, extraction, verification, and escalation, returning typed signals and review recommendations.

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

Provides over 1,000 creative ways to decline requests across four categories (polite, humorous, professional, and creative). The MCP server wraps a REST API to help users craft professional rejections through natural language interactions.

Enables AI assistants to interact with Terraform Cloud workspaces and runs, including checking run status, listing workspaces, and retrieving detailed information about workspaces and runs.

Enables management of Terraform infrastructure as code through 25 comprehensive tools for operations including plan/apply/destroy, state management, workspace management, and configuration file editing.

The Terraform MCP Server is a Model Context Protocol (MCP) server that integrates seamlessly with Terraform Registry and HCP Terraform APIs, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.

MCP server for managing Terraform infrastructure as code, enabling initialization, planning, applying, destroying, validating, and showing state of Terraform configurations.

An MCP server that exposes Terraform CLI operations as tools for Claude and other MCP-compatible AI assistants, enabling AI-driven infrastructure-as-code workflows including planning, applying, and validating Terraform configurations.

An advisory and generative copilot for Terraform that reviews existing scripts and generates compliant infrastructure using organization-specific rules.

Enables AI agents to manage Terraform modules by searching, inspecting, and scaffolding configurations from private GitHub repositories. Also provides backend S3 configuration for generated Terraform code.

A Model Context Protocol (MCP) server that lets Claude manage Terraform infrastructure through natural language.

An MCP server that wraps terraform-ls to provide Terraform language intelligence as MCP tools, enabling AI assistants to understand and navigate Terraform codebases.

Enables generating, validating, planning, and applying Terraform configurations to manage infrastructure through natural language.

A FastMCP-based server that provides a natural language interface to Terraform operations, enabling infrastructure management via simple English commands.

Generates structured prompts for Claude Code to create comprehensive Terraform test cases including unit, integration, and mock tests.

Enables Codex to delegate review and implementation tasks to the local Qoder CN CLI as background jobs, with two permission tiers and polling-based status updates.

Enables coding agents to answer from what is actually true in the current Terraform working directory: the provider schemas pinned in the lock file, saved plans, redacted state, and local or installed module interfaces. It also reports what a pinned provider upgrade would break, all read-only and without ever running init in the root module.

Exposes the local Claude Code CLI as a subagent for Codex, enabling background review and implementation jobs with two fixed permission tiers.

Enables AI assistants to search and retrieve information about Terraform providers and modules from the public Terraform registry, including detailed documentation, version information, and resource specifications.

Bridges a remote, cloud-hosted agent to your local machine, exposing Pi's coding tools (read, write, edit, ls, grep, find, bash, powershell) rooted at a directory you choose. It also adds a human channel so the agent can message, question, and wait on you through tool calls instead of a platform chat UI, with OAuth 2.1 or bearer-token authorization and no persistence between runs.

A Model Context Protocol (MCP) server for producing better Terraform through CLI analysis (tflint, checkov, trivy, kics, infracost), best-practice guidance from terraform-best-practices.com, cloud provider recommendations (Azure, AWS, GCP), and Terraform Registry resource and module guidance.

Bridges Claude Code CLI with Cursor IDE to use your existing Claude subscription without separate API costs.

Connects AI models to the Terraform Registry via MCP, enabling provider lookups, resource usage examples, and module recommendations for streamlined Terraform workflows.

Exposes a running DeepSeek Harness as an MCP endpoint so any other agent or script can create workspaces and sessions, hand coding tasks to the DSH agent, read and write files, run shell commands, and invoke permitted harness tools under the same sandbox, transcript, and permission policy as the DSH UI.

Enables AI coding assistants to run static analysis on GitHub repositories, raw code snippets, or local directories to detect cloud cost leaks in Terraform/AWS configs, PostgreSQL migration table-lock hazards, and OWASP/Next.js API security gaps. Each finding returns structured severity, line-level detail, and drop-in fixes.

Provides tools to execute Terraform commands, analyze plan outputs for resource changes, and generate detailed markdown reports. It supports custom environment variables and filtering patterns to streamline infrastructure analysis and management.

Converts REST APIs into MCP tools using Gradio, demonstrated with a local IBM Granite model via Ollama. Enables LLM clients to interact with any REST API endpoint through the MCP protocol.

Exposes Terraform/Terragrunt tooling as Claude Code tools for generating variables.tf and mock outputs automatically from input files.

A read-only MCP server that analyzes a supplied Terraform plan JSON file and returns resource identities, action/type/mode counts, and coverage warnings about proposed infrastructure changes. It never executes Terraform, applies changes, or connects to AWS, keeping analysis local and deterministic.