terraform-mcp-server
An MCP (Model Context Protocol) server that exposes tools for querying Terraform Registry information—provider documentation and module discovery/details—so an AI agent can retrieve and reason over Terraform Registry metadata for IaC development and automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security documentation is minimal in the provided README (only a contact/security policy link). The server is likely to make outbound calls to Terraform Registry, but TLS usage, certificate validation, proxy handling, logging behavior for any request data, and how secrets (if any) are handled are not specified. No auth/scopes are described, which limits security posture assessment.
⚡ Reliability
Best When
You want an agent to look up public Terraform Registry docs and module metadata through a standardized MCP tool interface (e.g., in VS Code/Claude Desktop agent mode).
Avoid When
You need fine-grained access control, custom auth integration, or strong guarantees about network egress/data exposure; also avoid use in contexts requiring explicit rate-limit and error-handling contracts beyond what’s documented in the README.
Use Cases
- • Automating Terraform provider and module discovery
- • Extracting and analyzing data from Terraform Registry
- • Getting detailed information about Terraform provider resources/data sources/functions
- • Exploring and understanding Terraform modules (inputs/outputs/examples/submodules)
Not For
- • Running or applying infrastructure changes to real environments
- • Handling confidential internal Terraform code or proprietary module registries (as described, it targets the public Terraform Registry)
- • Production-grade API authorization requirements without reviewing how the MCP server propagates/handles auth and networking
Interface
Authentication
No auth, API keys, or OAuth flows are described in the provided README. If the underlying Terraform Registry endpoints require/encourage authentication or have different rate limits, those details are not present here.
Pricing
No pricing information is provided; appears to be open-source self-hosted.
Agent Metadata
Known Gotchas
- ⚠ The README does not document rate-limit headers, retry/backoff guidance, or structured error codes, so agents may need defensive retry logic
- ⚠ Because outputs are dynamically generated and depend on the model/query, agents should validate/ground results against organizational security/compliance policies
- ⚠ Running via Docker implies network egress to Terraform Registry; agents should consider environment restrictions (firewalls/proxies) and potential caching needs
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for terraform-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.