Terraform MCP server
Search providers, modules, and HCP Terraform workspaces from your AI agents.
About
Connect Tracecat to Terraform to search providers, modules, and HCP Terraform workspaces for platform engineers, SREs, and security engineering agents. You can ground a remediation suggestion in the exact module version pinned in a workspace before any code change is proposed. From there, inspect run history, review Sentinel and OPA policy checks, and confirm which agent looked at which workspace with precision.
Setup
- 1
Create an access token
HashiCorp's Terraform MCP server uses a Terraform Enterprise or HCP Terraform API token for private registry and workspace tools. Public Terraform Registry tools work without a token. The token inherits the team and workspace permissions of the user that created it.
- 2
Select the
Terraformtile in the Tracecat MCP catalogOpen the
MCP catalogin your workspace, select theTerraformtile, and paste your access token. - 3
Enable
Terraformin your agentIn your
ai.agentaction orAgents→toolstab, selectTerraformfrom theMCP integrationsdropdown.
Tools
search_providersSearch the Terraform Registry for providers by name, keyword, or namespace.
get_provider_detailsFetch metadata, resources, and data sources for a specific provider version.
search_modulesSearch the Terraform Registry for community or private modules.
get_module_detailsFetch a module's inputs, outputs, and example usage at a given version.
list_workspacesList HCP Terraform or Terraform Enterprise workspaces in an organization.
get_workspaceFetch a workspace with its current run, VCS link, and Terraform version.
list_runsList runs for a workspace filtered by status, source, or actor.
get_runFetch a specific run with plan output, policy checks, and apply status.
list_policy_check_resultsInspect Sentinel or OPA policy check results for a run.