Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From terraform
Manages Terraform Cloud workspaces, monitors runs, retrieves plan/apply logs via TFC API with curl/jq, and searches providers/modules in the registry.
npx claudepluginhub bendrucker/claude --plugin terraformHow this skill is triggered — by the user, by Claude, or both
Slash command
/terraform:terraformThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **MCP tools** (`mcp__terraform`): workspace listing, run management, provider/module registry lookups
Searches Terraform registry for providers, modules, policies, and details; manages HCP Terraform workspaces, runs, variables for IaC workflows.
Retrieves plan and apply logs from Terraform Cloud runs via API. Use for debugging failed plans/applies, reviewing infrastructure changes, or examining TFC outputs. Requires TFE_TOKEN.
Guides Terraform/OpenTofu IaC operations: project layout, state management, module design, plan/apply safety, CI/CD pipelines, and secrets handling.
Share bugs, ideas, or general feedback.
mcp__terraform): workspace listing, run management, provider/module registry lookupsUse MCP tools to find and inspect runs:
list_workspaces to find the workspace by namelist_runs with the workspace ID to see recent runsget_run_details with the run ID for status, relationships, and timestampsThe run details include relationships.plan.data.id and relationships.apply.data.id — use these to fetch logs.
The MCP server does not expose log retrieval. Use the TFC API directly:
# Get the apply details (includes log-read-url)
curl -s \
-H "Authorization: Bearer $TFE_TOKEN" \
-H "Content-Type: application/vnd.api+json" \
https://app.terraform.io/api/v2/applies/{apply-id} | jq -r '.data.attributes."log-read-url"'
Then fetch the raw logs from the archivist URL (no auth needed — pre-signed):
curl -s "$(archivist_url)"
The same pattern works for plans via /api/v2/plans/{plan-id}.
See references/api.md for full API details.
$TFE_TOKEN is sourced from:
terraform login (stored at ~/.terraform.d/credentials.tfrc.json)The MCP server reads TFE_TOKEN from the environment. For curl calls, use it as a Bearer token.
Provider and module searches are available via MCP tools (search_providers, search_modules, provider_details, module_details). No curl needed for registry operations.