Agents Lookup

Use cases / IT & DevOps

Terraform drafts grounded in current provider docs

A coding agent looks up current Terraform provider and module docs through an MCP server before writing infrastructure code.

DifficultyIntermediate
Setup time1-2 hours
CategoryIT & DevOps

The use case

Models often write Terraform using old resource arguments or modules that no longer exist. HashiCorp's Terraform MCP server lets agents query the Terraform Registry for current provider docs and module details while writing code. An engineer asks for, say, an S3 bucket with logging and encryption, and the agent writes configuration that matches the current provider version. The engineer still runs plan, reads every change, checks for public exposure and cost, and applies through the normal pipeline. The agent should never run apply.

Example workflow

  1. Add the Terraform MCP server to your coding agent
  2. Describe the infrastructure you need
  3. Agent checks registry docs and writes configuration
  4. Run terraform plan and review every change
  5. Apply through CI with approval

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: