Terraform MCP
Reads Terraform provider documentation and registry metadata so an agent writes HCL against the real schema instead of inventing arguments.
What it does
Reads Terraform provider documentation and registry metadata so an agent writes HCL against the real schema instead of inventing arguments. It does not run plan or apply — this is a documentation and validation aid, not an execution engineer. Docker is the simplest way to keep it updated.
Install
docker run -i --rm hashicorp/terraform-mcp-server
Client configuration
Paste this into your MCP client config (Claude Desktop, Cursor, or any client that reads mcpServers), then restart the client.
{
"mcpServers": {
"terraform": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"hashicorp/terraform-mcp-server"
]
}
}
}
When to use it
Reach for this when the task needs infrastructure inside the agent loop. Skip it if a plain shell command or a one-off script is enough — every server you add costs context and adds a failure mode.
Other Go servers
- GitHub — Official GitHub server covering repositories, issues, pull requests, code search, and Actions
- Kubernetes MCP — Talks to the Kubernetes API directly instead of shelling out to kubectl, so an agent can list contexts, read pod logs, and apply manifests without parsing command output