LabscoMCP early access ↗
ExcoriateMCP SERVER

Terragrunt-Docs

Give your assistant the current Terragrunt documentation and open issues, so it stops guessing at block syntax.

by Excoriate ↗Framework & SDK Documentation LookupCommunity

LABSCO SUMMARY

Terragrunt blocks are exactly the thing an assistant invents plausibly and wrongly.

Editor tooling covers Terraform well and Terragrunt poorly, which is where confident, incorrect completions come from. Reading the current docs and the open issues in the same session covers both halves of that: what the syntax is, and what is currently broken. Start from the category listing — it is the map the other four tools navigate.

What it is

A documentation provider for Terragrunt. It reads the docs straight from the project's GitHub repository — categories, individual pages, or a whole category merged — and can also pull the open issues for context on known problems.

What you get

  • list-doc-categories — every documentation category, with the link for each
  • list-all-docs-by-category — the docs in one category, with their content
  • read-document-from-category — the full markdown of one document
  • read-all-docs-from-category — every doc in a category merged into a single response
  • get-all-open-issues — open issues from the Terragrunt repository with title, number, state, dates, body and labels

Requirements

A GitHub token, read from GITHUB_TOKEN, GH_TOKEN or GITHUB_PERSONAL_ACCESS_TOKEN — all five tools need it. Deno is the runtime; run it straight from JSR, from a local checkout, or from the Docker image built by the repository's Dockerfile.

Setup effort

One command plus a key — deno run -A jsr:@excoriate/mcp-terragrunt-docs@0.1.0, then supply credentials

See installation options