terraform-mcp-server

What it does

This server queries the Terraform Registry API to surface provider information, resource documentation, data source details, and module metadata. It provides 24 tools for browsing the public registry—providers, resources, data sources, and functions—and, with Terraform Cloud credentials, for managing workspaces, runs, and workspace resources. Supported operations range from read-only lookups (provider versions, resource argument details, module metadata) to state-changing calls (lock/unlock workspace, apply or cancel runs, create new runs).

Who it's for

Infrastructure engineers and DevOps practitioners writing Terraform configurations who want Claude to research providers, validate resource arguments, recommend modules, or troubleshoot Terraform Cloud runs without leaving the conversation.

Common use cases

• Look up argument details and example usage for a Terraform resource type.
• Search the Terraform Registry for modules matching a use case.
• Analyze failed Terraform Cloud workspace runs for troubleshooting.
• Generate Terraform code for migrating infrastructure between cloud providers.
• Scaffold new resource definitions with best-practice arguments.

Setup pitfalls

• This project is archived in favor of the official Terraform MCP server from HashiCorp; the last commit was 372 days ago and this version may diverge from current Registry and Cloud APIs.
• Terraform Cloud tools require a valid TFC_TOKEN environment variable; registry-only tools work without authentication but are rate-limited.
• The server supports destructive operations (lock/unlock workspace, apply runs). Ensure Claude has explicit instruction about what actions to take, and restrict the token to a limited organization if possible.
• Classified as high-risk due to network access and state-changing capabilities.