Terraform MCP Server 🔌 MCP server Open source

What it does

The Terraform MCP Server is HashiCorp's official MCP server for infrastructure-as-code work. HashiCorp is now part of IBM. The server links your coding agent to the public Terraform Registry, so the agent can write HCL against the current provider schemas, module inputs and versions instead of stale training data. If you add an HCP Terraform or Terraform Enterprise token, the agent can also browse your organisations, projects, workspaces, runs, variables and private registry modules. With an explicit opt-in, it can create or change workspaces and start runs. The server is a Go binary distributed as a Docker image under the MPL-2.0 licence, and its default instructions can be replaced with your own AGENTS.md guidance.

Tools it gives your agent

• Providers: search_providers, get_provider_details and get_latest_provider_version
• Modules: search_modules, get_module_details and get_latest_module_version
• Policies: search_policies and get_policy_details for Sentinel
• HCP Terraform/TFE: list organisations, projects, workspaces and runs, get workspace and run details, and use private registry lookups
• Gated operations: create_workspace, update_workspace, delete_workspace_safely and run actions, which all need ENABLE_TF_OPERATIONS=true

Works with

It runs locally over stdio through Docker, or you can self-host it as a Streamable HTTP service. The README has setup for VS Code, Cursor, Claude Desktop, Amazon Q Developer, Kiro CLI, Claude Code, Codex CLI, Gemini CLI (as an extension) and IBM Bob.

How to connect

The Claude Code command from the README:

claude mcp add terraform -s user -t stdio -- docker run -i --rm hashicorp/terraform-mcp-server

Cost and limits

The server is free, and Registry lookups need no account. The HCP Terraform tools need an API token, and the usual HCP Terraform or Terraform Enterprise plan pricing applies. The HTTP mode includes rate limits.

Safety notes

Operations that change things are off unless you set ENABLE_TF_OPERATIONS. Use a token scoped to the workspaces the agent should see. HashiCorp warns that Terraform data, which can include state details and variables, may be passed to the LLM, so only use trusted clients and models. For shared HTTP deployments, bind to localhost or use TLS, and set CORS origins and an organisation allowlist. Review generated plans before you apply them.