Terraform: MCP server, setup and security

What Terraform does

According to its repository: “Terraform ecosystem integration: provider discovery, module analysis and Terraform Registry API access for infrastructure-as-code workflows.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Terraform is listed under Cloud platforms, a category of 116 servers in the directory, where it ranks #11 by stars.

Installing and connecting Terraform

Distribution modes declared in the official MCP registry:

• Docker (OCI) image

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: Go.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Terraform. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on April 19, 2025, the hashicorp/terraform-mcp-server repository has 1,553 stars and 199 forks, with 11 open issues. It has more stars than 94% of the servers in the directory. It received changes this month. Version published in the registry: 1.4.1 (October 23, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.