Facets Module MCP Server
Related Servers
Alternatives to Facets Module MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables generating, validating, planning, and applying Terraform configurations to manage infrastructure through natural language.MIT
- AlicenseCqualityFmaintenanceEnables management of Terraform infrastructure as code through 25 comprehensive tools for operations including plan/apply/destroy, state management, workspace management, and configuration file editing.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents and users to author, scaffold, validate, mock, and run OpenTofu/Terraform native tests (.tftest.hcl), using the tofu CLI with Terraform fallback. It provides reference, generation, validation, and execution tools for the test framework.MIT
- FlicenseNot gradedqualityAmaintenanceExposes Terraform/Terragrunt tooling as Claude Code tools for generating variables.tf and mock outputs automatically from input files.-
- FlicenseNot gradedqualityCmaintenanceEnables Terraform HCL plan generation, drift detection, and strict human confirmation approval barriers for cloud infrastructure management.-
- AlicenseNot gradedqualityCmaintenance🌍 Terraform Model Context Protocol (MCP) Tool - An experimental CLI tool that enables AI assistants to manage and operate Terraform environments. Supports reading Terraform configurations, analyzing plans, applying configurations, and managing state with Claude Desktop integration. ⚡️371MIT
TDQS
Scored across 30 tools
Most tools have clearly distinct purposes, especially the write_* family which is carefully partitioned by file type. A few clusters (output type queries, file-writing helpers) could cause initial confusion, but their descriptions resolve the boundaries.
Naming is mostly consistent snake_case verb_noun: write_resource_file, list_all_intents, check_deployment_status, validate_module. A few odd exceptions like push_preview_module_to_facets_cp, test_already_previewed_module, and FIRST_STEP_get_instructions break the pattern.
30 tools is above the 25+ threshold and feels heavy for an MCP surface. The scope is broad, but several write, list, and query helpers could likely be consolidated.
The module lifecycle is well covered: instructions, file read/write, generation, forking, validation, import, preview, publish, and test. Minor gaps like missing delete/update operations for intents and output types prevent a perfect score.