MCP Server: Terraform AWS Provider Docs
@Excoriate
About MCP Server: Terraform AWS Provider Docs
Deno/TypeScript MCP Server providing context related to the AWS provider for Terragrunt documentation.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-terraform-aws-provider-docs": {
"command": "deno",
"args": [
"run",
"-A",
"jsr:@excoriate/mcp-terraform-aws-provider-docs@latest"
]
}
}
}Tools
9List all AWS resource documentation files with metadata
Fetch a single AWS resource documentation file by name or fuzzy search
List all AWS datasource documentation files with metadata
Fetch a single AWS datasource documentation file by name or fuzzy search
Retrieve open issues from Terraform AWS Provider GitHub repo
Fetch detailed information for a specific GitHub issue
Retrieve all releases from the Terraform AWS Provider GitHub repo
Fetch detailed information for a specific release by tag
Fetch detailed information for the latest release
Overview
What is MCP Server: Terraform AWS Provider Docs?
An MCP server built with Deno and TypeScript that provides AI agents or MCP clients with query access to Terraform AWS Provider documentation, including resources, datasources, GitHub issues, and release information. It is intended for IaC practitioners designing Terraform modules.
How to use MCP Server: Terraform AWS Provider Docs?
Install by adding a configuration entry to your MCP client (Claude Desktop, Cursor, Windsurf, or VSCode). The server can run via Deno directly or from JSR (jsr:@excoriate/mcp-terraform-aws-provider-docs), or using Docker. All tools require a valid GitHub token set as the GITHUB_TOKEN (or GH_TOKEN / GITHUB_PERSONAL_ACCESS_TOKEN) environment variable.
Key features of MCP Server: Terraform AWS Provider Docs
- Lists all AWS resource and datasource documentation files with metadata.
- Fetches detailed documentation for a specific resource or datasource by name or fuzzy search.
- Retrieves open GitHub issues and full issue details from the Terraform AWS Provider repo.
- Lists all provider releases and fetches release information by tag or latest release.
- Supports exact file name queries or natural language descriptions for documentation lookups.
- Can optionally include referenced issues when retrieving release details.
Use cases of MCP Server: Terraform AWS Provider Docs
- Quickly discover available AWS resources and datasources while writing Terraform configurations.
- Retrieve up‑to‑date documentation for any AWS resource to ensure correct arguments and attributes.
- Investigate open GitHub issues to understand whether a Terraform behavior is expected or related to a known bug.
- Check the latest provider release notes and linked issues before planning upgrades.
FAQ from MCP Server: Terraform AWS Provider Docs
What tools does the server provide?
It offers tools such as list-resources, get-resource-doc, list-datasources, get-datasource-doc, get-open-issues, get-issue, list-all-releases, get-release-by-tag, and get-latest-release.
Does this MCP server require a GitHub token?
Yes, all tools require a valid GitHub token. Set it as GITHUB_TOKEN, GH_TOKEN, or GITHUB_PERSONAL_ACCESS_TOKEN in the server's environment.
What runtime does it need?
It is a Deno/TypeScript project. You can run it using Deno (with the -A flag) or via the provided Docker image.
Can I install it in my IDE?
Yes, it supports Claude Desktop, Cursor, Windsurf, and VSCode. Each requires a configuration file (e.g. claude_desktop_config.json, ~/.cursor/mcp.json) with the appropriate command and arguments.
Does the server cache or store any data locally?
The README does not mention local caching or data storage. All queries appear to fetch data live from the Terraform AWS Provider registry and GitHub.
Frequently asked questions
What tools does the server provide?
It offers tools such as `list-resources`, `get-resource-doc`, `list-datasources`, `get-datasource-doc`, `get-open-issues`, `get-issue`, `list-all-releases`, `get-release-by-tag`, and `get-latest-release`.
Does this MCP server require a GitHub token?
Yes, all tools require a valid GitHub token. Set it as `GITHUB_TOKEN`, `GH_TOKEN`, or `GITHUB_PERSONAL_ACCESS_TOKEN` in the server's environment.
What runtime does it need?
It is a Deno/TypeScript project. You can run it using Deno (with the `-A` flag) or via the provided Docker image.
Can I install it in my IDE?
Yes, it supports Claude Desktop, Cursor, Windsurf, and VSCode. Each requires a configuration file (e.g. `claude_desktop_config.json`, `~/.cursor/mcp.json`) with the appropriate command and arguments.
Does the server cache or store any data locally?
The README does not mention local caching or data storage. All queries appear to fetch data live from the Terraform AWS Provider registry and GitHub.
Basic information
More Cloud & Infrastructure MCP servers
🐳 docker-mcp
QuantGeekDevA docker MCP Server (modelcontextprotocol)

Nippy
NippyNippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the
Firebase MCP
gannonh🔥 Model Context Protocol (MCP) server for Firebase.
MCP Server that interacts with Azure AI Foundry (experimental)
azure-ai-foundryA MCP Server for Azure AI Foundry: it's now moved to cloud, check the new Foundry MCP Server
Run Model Context Protocol (MCP) servers with AWS Lambda
awslabsRun existing Model Context Protocol (MCP) stdio-based servers in AWS Lambda functions
Comments