Terraform MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERRAFORM_WORKING_DIR | No | The default working directory for Terraform operations. If not set, the server will use the current working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tf_versionA | Get Terraform version |
| tf_initB | Initialize Terraform working directory |
| tf_validateC | Validate Terraform configuration |
| tf_planD | Create execution plan |
| tf_applyD | Apply Terraform changes |
| tf_destroyC | Destroy Terraform resources |
| tf_outputD | Get Terraform outputs |
| tf_state_listC | List resources in state |
| tf_state_showC | Show resource in state |
| tf_state_rmC | Remove resource from state |
| tf_state_mvC | Move resource in state |
| tf_importC | Import existing resource into state |
| tf_refreshC | Refresh state |
| tf_fmtC | Format Terraform files |
| tf_workspace_listC | List workspaces |
| tf_workspace_selectC | Select workspace |
| tf_workspace_newD | Create workspace |
| tf_workspace_deleteC | Delete workspace |
| tf_providersD | List providers |
| tf_graphC | Generate resource graph (DOT format) |
| tf_taintC | Mark resource for recreation |
| tf_untaintC | Remove taint from resource |
| tf_show_planC | Show saved plan file |
| tf_list_filesC | List Terraform files in directory |
| tf_read_fileC | Read a Terraform file |
| tf_write_fileC | Write a Terraform file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Each tool targets a distinct Terraform operation (e.g., apply, destroy, plan, state management, workspaces) with no overlap. Descriptions are clear enough to differentiate.
All tools follow a consistent 'tf_' prefix with a verb_noun pattern (e.g., tf_apply, tf_state_list, tf_workspace_new). No mixing of conventions.
26 tools cover the full lifecycle of Terraform operations—init, plan, apply, destroy, state, workspaces, file ops, etc. Each tool serves a clear purpose without bloat.
The set includes all major Terraform workflows: initialization, planning, applying, destroying, state management, workspace management, file operations, formatting, validation, import, output, and more. No critical gaps identified.