Skip to main content
Glama
RajeevSirohi

mcp-server-terraform

by RajeevSirohi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

tf_apply

Destructive

Preview Terraform changes with a plan, then confirm to apply them to real infrastructure.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
varsNoVariable overrides in key=value format, e.g. ["region=us-east-1"]
targetNoLimit operation to a specific resource address, e.g. aws_instance.web
varFileNoPath to a .tfvars or .tfvars.json file
workdirYesAbsolute or relative path to the directory containing .tf files
planFileNoPath to a saved plan file from tf_plan (recommended for exact apply)
confirmedNoMust be true to actually apply. Omit or set false to preview only.
workspaceNoTerraform workspace to use (default: current workspace)

Tool Definition Quality

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description discloses the two-step flow, emphasizing safety and the behavior difference between confirmed=false (preview) and confirmed=true (apply), complementing the destructiveHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise, well-structured description with no wasted words; key safety instructions are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Explains return behavior (plan output vs. actual apply), mentions optional parameters like planFile, and provides sufficient context for a destructive action tool without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions; description adds context for the 'confirmed' parameter via the two-step flow, enhancing understanding beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Apply Terraform changes to real infrastructure' and explains the two-step safety flow, distinguishing it from sibling tools like tf_plan (preview only) and tf_destroy (destroy resources).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to first call without confirmed=true to preview, then with confirmed=true after reviewing diff, and warns against passing confirmed=true without prior plan output.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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