Terragrunt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_docsA | Search Terragrunt documentation for HCL blocks, CLI commands, functions, and IaC patterns. Modes: search, list sections, get section content, or find code examples. |
| function_referenceC | Get Terragrunt built-in function details (find_in_parent_folders, dependency, read_terragrunt_config, etc.) or list all available functions by category. |
| cli_referenceB | Get current Terragrunt CLI command help (run --all, browse, plan, apply, hcl validate, etc.) or list commands by category. |
| get_hcl_config_referenceB | Get current Terragrunt HCL block and attribute documentation with syntax and examples, including stacks, feature flags, exclusions, error handling, catalogs, and engines. |
| get_guidanceA | Get Terragrunt best practices, block comparisons (dependency vs dependencies), DRY patterns, or experiment status (type=experiments lists active/completed experiments and how to enable them) for infrastructure-as-code organization. |
| build_configA | Generate or write Terragrunt HCL configuration files (terragrunt.hcl). Use cases: remote_state backends (S3, GCS, Azure), provider generation, dependency blocks, hooks, inputs, and cicd (CI/CD-ready config for GitHub Actions, GitLab, Azure DevOps). |
| diagnose_terragrunt_errorA | Diagnose Terragrunt and Terraform error messages with root cause analysis and solutions. Handles dependency cycles, state lock errors, provider issues, and HCL syntax problems. |
| get_server_metricsB | Get Terragrunt MCP server metrics: cache hit rates, tool invocation counts, response times, and memory usage for observability. |
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 8 tools
Most tools are distinct, but search_docs explicitly covers HCL blocks, CLI commands, and functions, overlapping with function_reference, cli_reference, and get_hcl_config_reference. The more specific reference tools remain identifiable, though an agent could easily pick the wrong one for a given documentation lookup.
The naming pattern is mixed: get_server_metrics, get_hcl_config_reference, and get_guidance use a get_ prefix, while function_reference and cli_reference drop the verb, and search_docs/build_config/diagnose_terragrunt_error use different verb styles. The names are still readable and mostly signal their purpose, but there is no consistent verb_noun convention.
Eight tools is a well-scoped set for a Terragrunt-oriented server covering documentation, references, guidance, config generation, error diagnosis, and observability. Each tool appears to justify its place without redundancy or bloat.
The server covers Terragrunt documentation, function/CLI/HCL references, best practices, config generation, and error diagnosis, which covers the apparent domain well. Minor gaps exist, such as no tool to read/validate an existing terragrunt.hcl or execute Terragrunt commands, but these are not clearly required by the server's stated purpose.