mcpField
M
MCP Server: Terragrunt Docs Provider

MCP Server: Terragrunt Docs Provider

Local
github.com/ExcoriateMemory & Knowledge20Updated 79w ago

About MCP Server: Terragrunt Docs Provider

MCP Server: Terragrunt Docs Provider is an MCP server built with Deno and TypeScript that supplies Terragrunt documentation and GitHub issues as context for AI assistants. It is aimed at users writing Terragrunt configurations, where current docs help reduce incorrect suggestions.

Key features

  1. 01List Terragrunt documentation categories
  2. 02Read a single document from a category
  3. 03Merge all documents in a category
  4. 04Retrieve open issues from the Terragrunt repository

Use cases

  1. 01Writing or checking Terragrunt configurations against current docs
  2. 02Tracking open issues and discussions in the Terragrunt project
  3. 03Supplying documentation content to a search feature

MCP support

This project is an MCP server that exposes tools for listing documentation categories, reading documents and fetching open issues to MCP clients. The GitHub-backed tools require a GitHub token set as an environment variable.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MCP Server: Terragrunt Docs Provider

Language License

A Model Context Protocol (MCP) server built with Deno and TypeScript, designed to provide contextual information related to Terragrunt.

Overview

This server acts as an MCP provider, exposing tools and resources that allow AI agents or other MCP clients to query information about Terragrunt documentation and development information, such as GitHub issues.

  • Watch a realistic demo 📺 on Claude Desktop here

Why?

When writing IaC configurations, mostly in terragrunt, the IDE support isn't that good, in VSCode the terraform plugin is good, but not for terragrunt; it does not recognize the terragrunt blocks and does not provide any autocompletion. When interacting with AI autocompletion, it's common to get incorrect results, or false-positive linting errors. With this MCP server, you can provide to your LLM/AI assistant the latest documentation and issues from the Terragrunt GitHub repository, so it can use that to provide you with the most accurate information.

Tools

Note: All tools require a valid GitHub token set as an environment variable: GITHUB_TOKEN, GH_TOKEN, or GITHUB_PERSONAL_ACCESS_TOKEN.

Tool NamePurposeInputsOutputsUse Case
list-doc-categoriesRetrieve all documentation categories from Terragrunt docs.NoneArray of objects with name (string) and link (string) propertiesUse when you need to explore the available documentation structure or when building a documentation navigation system. This is typically the first tool to call when starting to work with Terragrunt docs.
list-all-docs-by-categoryList all docs in a specific category.category (string)Array of objects with name (string), link (string), and content (string)Use when you need to see all available documentation within a specific category, such as when building a category-specific documentation viewer or when you need to scan through all docs in a particular area.
read-document-from-categoryRead a specific doc from a category.category (string), document (string)Object containing content (string) with the full markdown contentUse when you need to access the complete content of a specific document, such as when implementing documentation search or when you need to reference specific documentation in your application.
read-all-docs-from-categoryRetrieve and merge all docs in a category into one response.category (string)Object containing content (string) with all docs merged into oneUse when you need a comprehensive view of all documentation within a category, such as when building a documentation search feature or when you need to analyze the complete documentation set for a specific topic.
get-all-open-issuesRetrieve all open issues from Terragrunt GitHub repo.all (boolean, optional)Array of objects with title (string), number (number), state (string), created_at (string), updated_at (string), body (string), and labels (string[])Use when you need to track or analyze current issues in the Terragrunt project, such as when building an issue dashboard, performing issue triage, or when you need to stay updated with the latest project challenges and discussions.

Setup

  1. Install Deno:

  2. Clone the repository:

    git clone https://github.com/Excoriate/mcp-terragrunt-docs.git
    cd mcp-terragrunt-docs
    
  3. Set your GitHub token as an environment variable:

    • On Unix/macOS:

      export GITHUB_TOKEN=ghp_xxx... # or GH_TOKEN or GITHUB_PERSONAL_ACCESS_TOKEN
      
    • On Windows (cmd):

      set GITHUB_TOKEN=ghp_xxx...
      

Note: You can also set the token in the .env file.

  1. Run the MCP server:

    # directly using deno
    deno run -A main.ts
    
    # Using the justfile
    just run
    
    # You can also debug it, and inspect it locally
    just inspect
    

The most straightforward method is to use it directly from JSR (Javascript Registry ❤️)

# export your github token
export GITHUB_TOKEN=ghp_xxx...

# run it
deno run -A jsr:@excoriate/[email protected]
Usage with Claude Desktop

To use this Deno-based MCP server with Claude Desktop, add the following to your claude_desktop_config.json:

Using Deno
{
  "mcpServers": {
    "terragrunt_docs": {
      "command": "deno",
      "args": [
        "run",
        "-A",
        "main.ts"
      ],
      "env": {
        "GITHUB_TOKEN": "<YOUR_TOKEN>"
      },
    }
  }
}
Using Docker
{
  "mcpServers": {
    "terragrunt_docs": {
      "command": "docker",
      "args": [
        "run",
        "-e", "GITHUB_TOKEN=<YOUR_TOKEN>", "mcp-terragrunt-docs"
      ],
      "env": {
        "GITHUB_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Using JSR
{
  "mcpServers": {
    "terragrunt_docs": {
      "command": "deno",
      "args": [
        "run",
        "-A",
        "jsr:@excoriate/[email protected]"
      ],
      "env": {
        "GITHUB_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Build the Docker image
docker build -t mcp-terragrunt-docs .
Run the MCP server in Docker
docker run -it --rm \
  -e GITHUB_TOKEN=ghp_xxx... \
  mcp-terragrunt-docs
  • Replace ghp_xxx... with your GitHub Personal Access Token with appropriate permissions.
  • You can also use GH_TOKEN or GITHUB_PERSONAL_ACCESS_TOKEN as the environment variable name.
  • If you want to use a local .env file, you can pass it with --env-file .env.

Contributing

See docs/CONTRIBUTING.md for detailed contribution guidelines, including setup, code style, PR process, and codebase structure reference.

Security

See SECURITY.md for the project's security policy, including how to report vulnerabilities and responsible disclosure guidelines.

License

This project is licensed under the MIT License.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.