Skill

terraform

Manages Terraform Cloud workspaces, monitors runs, retrieves plan/apply logs via TFC API with curl/jq, and searches providers/modules in the registry.

Terraform

Bash

infrastructure

devops

Install

npx claudepluginhub bendrucker/claude --plugin terraform

Tool Access

This skill is limited to using the following tools:

mcp__terraformBash(curl:*)Bash(jq:*)

Preview

- **MCP tools** (`mcp__terraform`): workspace listing, run management, provider/module registry lookups

Supporting Assets

references/api.md

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars10

Parent Repo Forks1

Last CommitFeb 9, 2026

Actions

View Source View Plugin View on GitHub View README

Terraform

Tool Selection

MCP tools (mcp__terraform): workspace listing, run management, provider/module registry lookups
curl: plan and apply log retrieval — the MCP server does not expose these endpoints

Run Monitoring

Use MCP tools to find and inspect runs:

list_workspaces to find the workspace by name
list_runs with the workspace ID to see recent runs
get_run_details with the run ID for status, relationships, and timestamps

The run details include relationships.plan.data.id and relationships.apply.data.id — use these to fetch logs.

Fetching Plan/Apply 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.

Authentication

$TFE_TOKEN is sourced from:

terraform login (stored at ~/.terraform.d/credentials.tfrc.json)
Or set directly as an environment variable

The MCP server reads TFE_TOKEN from the environment. For curl calls, use it as a Bearer token.

Registry

Provider and module searches are available via MCP tools (search_providers, search_modules, provider_details, module_details). No curl needed for registry operations.