MCPSERV.CLUB
Excoriate

Terragrunt Docs Provider

MCP Server

Provide Terragrunt docs and issues to AI agents via MCP

Stale(50)
15stars
1views
Updated Sep 25, 2025

About

A Deno/TypeScript MCP server that exposes tools for querying Terragrunt documentation and GitHub issues, enabling AI assistants to deliver up‑to‑date IaC guidance and accurate autocompletion for Terragrunt configurations.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

Overview

The Terragrunt Docs Provider is an MCP server that supplies AI assistants with up‑to‑date, structured information about Terragrunt—a popular tool for managing Terraform modules. By exposing a set of high‑level tools, the server lets LLMs query the official documentation and GitHub issue tracker in a single, consistent interface. This eliminates the need for developers to manually search the web or maintain local copies of documentation, and it keeps the AI’s knowledge current with the latest releases and community discussions.

When writing infrastructure-as-code, many IDEs lack robust support for Terragrunt’s custom syntax. Even the best Terraform extensions in VS Code fail to recognize Terragrunt blocks, leading to incomplete autocompletion and false linting warnings. The MCP server addresses this gap by providing an AI‑friendly data source: the latest docs, categorized and searchable, plus real‑time issue data from the Terragrunt GitHub repository. An assistant can now ask, “What does the block do?” or “Show me open issues about provider errors,” and receive precise, authoritative answers without leaving the chat.

Key capabilities include:

  • Documentation browsing – list categories, retrieve all docs in a category, or read a single markdown file.
  • Content aggregation – merge all docs in a category into one coherent response, ideal for building searchable knowledge bases.
  • Issue tracking – fetch all open GitHub issues, enabling the assistant to surface current community pain points or feature requests.
  • Environment‑safe access – all tools require a GitHub token, ensuring secure API calls without exposing credentials in the prompt.

Typical use cases span from IDE assistants that auto‑complete Terragrunt syntax to chatbots that answer questions about best practices, and even continuous‑integration pipelines that need to validate module usage against the latest documentation. By integrating this MCP server into an AI workflow, developers gain a single source of truth that keeps pace with Terragrunt’s evolution, reduces friction in IaC development, and empowers assistants to deliver reliable, context‑aware guidance.