Category · Infrastructure MCP servers
Terraform MCP Server: HashiCorp's Official IaC Integration
The Terraform MCP server is HashiCorp's official bridge between AI assistants and Terraform, covering Registry lookups and infrastructure-as-code workflows. Its most immediately useful job is unglamorous: resolving the correct provider and module documentation for the version you are actually pinned to, so generated HCL references arguments that exist. For anyone who has watched an assistant confidently invent a resource attribute, that alone justifies the install.
What this category covers
Infrastructure MCP servers connect assistants to the systems that define and run your infrastructure. Terraform MCP is the official HashiCorp implementation, focused on the Terraform Registry — providers, modules, and their documented arguments — and on supporting IaC workflows. It is open source and free. Around it sit servers for the platforms Terraform provisions into, such as the AWS MCP server, and for the runtime systems that come after.
How it works
Register the server in your MCP client and it exposes tools for searching the Terraform Registry and retrieving provider and module documentation. When you ask an assistant to write HCL for a given resource, it can look up the real schema for the provider version in use rather than generating from memory. That distinction matters most on fast-moving providers, where an argument renamed two minor versions ago is exactly the kind of detail a model gets wrong. For the container layer underneath, see the Docker MCP server.
Buying guide
Use the Terraform MCP server for reading and authoring, not for applying. Registry lookups, module discovery, and schema-accurate HCL generation are where it earns its place; letting an assistant run apply against production infrastructure is a different risk category entirely, and the safer pattern is that the assistant writes the change, opens a pull request through GitHub MCP, and a human approves the plan. Pair it with the cloud provider server matching your estate — the Azure MCP server, Cloudflare MCP, or Kubernetes MCP — so the assistant can compare what the code declares against what actually exists, which is where most infrastructure surprises live. Keep credentials scoped read-only wherever the workflow allows it.
The Tools, Ranked
HashiCorp's official server for Terraform Registry lookups and infrastructure-as-code workflows.
Inspect and manage clusters, which is usually where Terraform-provisioned infrastructure actually runs.
Connect to storage, databases, Key Vault, and other Azure services — the live counterpart to what Terraform declares.
Manage Workers and Cloudflare settings, commonly Terraform-managed and just as commonly inspected manually.
Container and image management for the layer between IaC and running services.
Manage Vercel deployments and projects for teams whose front end sits outside the Terraform-managed estate.
Query errors after a change ships — closing the loop between an infrastructure edit and its consequences.
IaC changes go through pull requests. Repository access lets the assistant read the diff and prior context before proposing a change.