TerraformMCP Server

HashiCorp's official MCP server for infrastructure-as-code work. It puts the Terraform Registry and, optionally, your HCP Terraform or Terraform Enterprise organisation behind a tool interface, so an agent writing HCL can look up what actually exists instead of inventing provider arguments that do not.

Registry lookups are the point

Most agent-authored Terraform fails the same way: a plausible resource attribute that no version of the provider ever had. Direct integration with the public Terraform Registry APIs for providers, modules, and policies turns that guess into a lookup — the agent can check the real schema, find a module that fits, and cite the version it read.

Workspace operations

With TFE_ADDRESS and TFE_TOKEN configured, the server extends to HCP Terraform and Terraform Enterprise: creating, updating, and deleting workspaces, managing variables, tags, and runs, listing organisations and projects, and reaching private registry content alongside the public one.

Transports and operations

Both stdio and StreamableHTTP transports are supported, with configurable host, port, endpoint path, CORS, and stateful or stateless session modes — so the same binary serves a local desktop client and a hosted deployment. In HTTP mode it exports OpenTelemetry metrics for tool-call volume, latency, and failures, which is what you want before letting agents drive infrastructure at any scale.

Operating notes

HashiCorp is explicit that the server may surface Terraform data to whichever client and model you connect, and recommends against untrusted clients. Outputs are generated dynamically and vary by model and client, so review recommendations against your own security, cost, and compliance requirements before applying them. Distributed as a Docker image; the pinned tag shown in the docs at time of writing is 0.2.3.