Skip to main content
Glama
RajeevSirohi

mcp-server-terraform

by RajeevSirohi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALLOWED_TOOLSNoComma-separated list of allowed tools, e.g. 'tf_plan,tf_output'.
AUDIT_LOG_PATHNoFile path for audit logging. Every tool call is appended as a JSON line.
ALLOW_ONLY_READONLY_TOOLSNoIf set to 'true', only readonly tools are available (tf_validate, tf_plan, tf_output).
ALLOW_ONLY_NON_DESTRUCTIVE_TOOLSNoIf set to 'true', blocks destructive tools (tf_apply, tf_destroy, tf_state mv/rm).

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tf_validateA

Validate Terraform configuration files for syntax and internal consistency. Does not access remote state or APIs.

tf_planA

Run terraform plan and return a human-readable diff of what will change. Safe — makes no changes to infrastructure.

tf_outputA

Read Terraform output values from the current state. Returns all outputs as JSON, or a specific output by name.

tf_preflightA

Check which cloud providers are used in a Terraform workspace and verify authentication status for each. Call this before plan or apply to catch credential issues early.

tf_driftA

Detect infrastructure drift — resources that were changed outside of Terraform (e.g. manually in the cloud console). Runs a refresh-only plan and reports differences between state and reality. Read-only, makes no changes.

tf_applyA

Apply Terraform changes to real infrastructure.

TWO-STEP SAFETY FLOW:

  1. Call without confirmed=true → runs terraform plan, shows the diff, returns without applying.

  2. Call with confirmed=true after reviewing the diff → actually applies the changes.

Never pass confirmed=true without first showing the plan output to the user.

tf_destroyA

Destroy all Terraform-managed infrastructure in the workspace.

TWO-STEP SAFETY FLOW:

  1. Call without confirmed=true → shows the destroy plan (what will be deleted).

  2. Call with confirmed=true after the user explicitly approves → destroys everything.

This is irreversible. Always show the plan and get explicit user approval first.

tf_stateA

Manage Terraform state. Supports the following operations:

  • list: List all resources in state

  • show: Show attributes of a specific resource

  • mv: Move/rename a resource in state (use with care)

  • rm: Remove a resource from state without destroying it (destructive)

tf_resourceA

Resource-level state operations:

  • import: Bring an existing cloud resource under Terraform management (requires address + id)

  • taint: Mark a resource for recreation on next apply (requires address)

  • untaint: Remove the taint mark (requires address)

  • refresh: Sync state with real infrastructure (accepts drift into state)

tf_initA

Initialize a Terraform working directory. Downloads providers and modules. Run this before plan or apply on a fresh workspace.

tf_workspaceA

Manage Terraform workspaces. Supports:

  • list: List all workspaces and show which is active

  • show: Show the current workspace name

  • select: Switch to a workspace

  • new: Create a new workspace

Prompts

Interactive templates invoked by user choice

NameDescription
tf-diagnoseSystematically diagnose a Terraform plan or apply failure
tf-loginDetect cloud providers in a Terraform workspace and guide the user through authentication

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RajeevSirohi/mcp-server-terraform'

If you have feedback or need assistance with the MCP directory API, please join our Discord server