terraform-best-practices-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFRACOST_API_KEY | No | Infracost API key for cloud-backed cost estimates. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_tflintC | Run tflint against a Terraform project directory. |
| run_checkovC | Run checkov over a Terraform directory. |
| run_trivyB | Run trivy config scanning against Terraform code. |
| run_kicsB | Run kics IaC scanning against Terraform code. |
| run_infracostB | Run infracost breakdown for a Terraform directory. |
| fetch_terraform_best_practicesB | Fetch Terraform best-practice guidance from curated checks and optional live summaries from terraform-best-practices.com. |
| fetch_provider_best_practicesA | Fetch Terraform best-practice guidance for Azure, AWS, or GCP from curated checks and optional live provider docs summaries. |
| fetch_terraform_registry_guidanceB | Fetch Terraform Registry best-practice guidance with optional provider/resource/module context. |
| analyze_terraform_codeB | Analyze Terraform code structure, modularity, variables, and best practices. |
| analyze_terraform_performanceC | Analyze Terraform code for performance risks and optimization opportunities. |
| analyze_state_managementB | Assess Terraform backend/state strategy and recommend safer state management patterns. |
| generate_cost_reportB | Generate a comprehensive cost report from infracost output with optimization suggestions. |
| generate_terraform_module_docsB | Generate markdown documentation for Terraform modules from source code. |
| recommend_terraform_modulesB | Recommend Terraform Registry modules based on code patterns and deployment intent. |
| suggest_security_hardeningB | Analyze security scan output and suggest hardening steps to improve infrastructure security. |
| suggest_terraform_architectureA | Suggest Terraform architecture and repository patterns for multi-environment infrastructure. |
| suggest_terraform_testing_strategyB | Recommend Terraform testing strategy and CI stages based on risk and change cadence. |
| generate_compliance_summaryB | Generate a compliance summary report from multiple security scan outputs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct aspect of Terraform best practices, such as state management, code analysis, performance, fetching guidance from different sources, generating reports, running various security scanners, and suggesting improvements. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun pattern using present-tense verbs (analyze, fetch, generate, recommend, run, suggest) and snake_case. The naming is predictable and clearly indicates the tool's action and target.
With 18 tools, the server covers analysis, fetching guidance, generating outputs, running external tools, and providing suggestions. This is a well-scoped set for a best-practices advisor, not too few or too many.
The tool surface covers the full workflow for Terraform best practices: analysis, fetching external guidance, running security scanners, generating documentation and reports, and providing actionable suggestions. There are no obvious gaps for its stated purpose.