Terraform Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_run_statusB | Get the current run status for a Terraform Cloud workspace |
| list_workspacesB | List all workspaces in a Terraform Cloud organization |
| get_workspace_detailsB | Get detailed information about a Terraform Cloud workspace |
| get_run_detailsB | Get detailed information about a specific Terraform Cloud run by its ID |
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 4 tools
The tools are mostly distinct, with clear separation between workspace operations (list_workspaces, get_workspace_details) and run operations (get_run_details, get_run_status). However, get_run_details and get_run_status could potentially be confused since both relate to run information, though their descriptions differentiate them as 'detailed information' versus 'current status'.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_run_details, list_workspaces). The verbs 'get' and 'list' are used appropriately and predictably throughout the set.
With only 4 tools, the server feels thin for managing Terraform Cloud resources. While it covers basic read operations, the scope suggests more comprehensive management (e.g., create/update/delete operations) would be expected, making the count borderline for the domain.
The toolset is severely incomplete for Terraform Cloud management. It only provides read operations (get and list) with no ability to create, update, or delete workspaces, runs, or other resources. This will cause significant agent failures when attempting full lifecycle management.