Terraform MCP Server
Generate more accurate Terraform and automate workflows for HCP Terraform and Terraform Enterprise
Publisher claimed. No tool list reported, and Pod has not connected to this server.
Status
Pod has not dialled Terraform yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.
Connect
Published as docker.io/hashicorp/terraform-mcp-server:1.0.0 on oci. Runs locally.
Known issues
62 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded — those are release checklists and internal refactors, not things that will go wrong for you. Showing 12.
Most discussed
Feature request: Add team, project, and team access management tools
Use-cases
When automating Terraform Cloud/Enterprise setup for new teams or projects, three operations are always required but currently missing from the MCP server:
- Create a project
- Create a team
- Grant team access to a project or workspace
Today these must be done via raw API calls (curl) or the TFC UI, which breaks the automation flow when using an MCP client. An agent can create workspaces, manage variables, and trigger runs, but cannot set up the organizational
Read the thread · 2026-05-21 · open · external user · 3 comments
Provider search for 'keycloak' returns community provider instead of official
Description
When searching for 'keycloak' in the Terraform Provider Registry via terraform-mcp-server, the top result is a community provider from the user mrparkers rather than the official Keycloak provider. This leads to confusion for users who expect official providers to be prioritized.
Testing plan
- Search for 'keycloak' using the provider search functionality in terraform-mcp-server.
- Observe the returned providers and note that the community provider (mrparkers/keycloak) app
Read the thread · 2025-09-23 · open · external user · 3 comments
[FEAT] Terraform documentation tool
Suggestion: Can you please make additional toolset that would be able to pull latest terraform configuration documentation from https://github.com/hashicorp/terraform or https://developer.hashicorp.com/terraform/language? Something like #getTerraformDocs.
Use case: For example it is very hard to use Copilot and included with it LLM's to write terraform tests. Without actual tests schema they don't know how to write native terraform tests and create some non usable hybrids with terrafo
Read the thread · 2025-07-09 · closed · external user · 6 comments
Unable to use MCP behind Zscaler Internet Access proxy
We leverage Zscaler Internet Access with TLS inspection as part of our base desktop images. Because of this, all requests to external sites receive an intermediate certificate anchored in a Zscaler root and is causing the MCP server calls out to the registry to fail:
tls: failed to verify certificate: x509: certificate signed by unknown authority
We either need the image to include known trusted intermediates (like the different Zscaler intermediates) or a way to pass in our own .pem file to
Read the thread · 2025-06-12 · closed · external user · 3 comments
[FEAT] Add support for fetching the latest provider version
First, I would like to thank you for contributing this MCP server.
A request I often ask to my coding agent is "include the latest version of this provider". It would be helpful if the MCP server could expose the provider "metadata".
Read the thread · 2025-06-04 · closed · external user · 4 comments
Most recent
Add a whoami tool
Use-cases
I have more than one token that I use for accessing differ
Read the thread · 2026-08-11 · closed · outside contributor · 1 comment
get_apply_logs hangs then times out if the apply is in a pending state.
terraform-mcp-server version
Use-cases
As a module publisher in our private registry, we need to p
Read the thread · 2026-08-07 · open · external user · 0 comments
retrieve private registry submodule information
currently the get_private_module_details tool only returns top-level module info and does not expose any additional information at the individual submodule level
expected outcome: expose private registry submodule information in the same manner as top-level modules.
Read the thread · 2026-07-31 · open · external user · 0 comments
create_no_code_workspace: elicitation marks every module variable required and rejects empty values (defaults/optionality not honoured
Version
hashicorp/terraform-mcp-server:latest (code analysis against main @ ab3929d44fe2a8c37d3cf8d267335f1a8e4f7f01)
Description create_no_code_workspace collects module variables via an elicitation/create request. The way that request is built and validated makes it impossible to create most real no-code modules — any module with an optional or defaulted input variable — even from a client that fully supports elicitation.
Two code paths combine to cause this:
Every input variable i
Read the thread · 2026-07-28 · closed · external user · 0 comments