Can I use Terraform Cloud as a CLI?

Yes. KosmoKrator exposes a Terraform Cloud CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Terraform Cloud through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Terraform Cloud tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Terraform Cloud credentials stored?

Terraform Cloud credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Terraform Cloud MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Terraform Cloud CLI for Headless Automation

Use the Terraform Cloud CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API token auth

Submit Terraform Cloud feedback View package source

Terraform Cloud CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Terraform Cloud CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Terraform Cloud CLI for Headless Automation
kosmokrator integrations:configure terraform --set api_token="$TERRAFORM_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call terraform.terraform_list_workspaces '{"organization":"example_organization","pageNumber":1,"pageSize":1}' --json

Discovery Before Execution

Agents and scripts can inspect Terraform Cloud docs and schemas before choosing a function.

kosmo integrations:docs terraform --json
kosmo integrations:docs terraform.terraform_list_workspaces --json
kosmo integrations:schema terraform.terraform_list_workspaces --json
kosmo integrations:search "Terraform Cloud" --json
kosmo integrations:list --json

Useful Terraform Cloud CLI Functions

Function	Type	Parameters	Description
`terraform.terraform_list_workspaces`	Read	organization, pageNumber, pageSize	List workspaces in a Terraform Cloud organization. Returns workspace IDs, names, Terraform versions, and locked status.
`terraform.terraform_get_workspace`	Read	workspaceId	Get details of a specific Terraform Cloud workspace by its ID. Returns workspace configuration, status, and VCS settings.
`terraform.terraform_list_runs`	Read	workspaceId, pageNumber, pageSize	List runs for a Terraform Cloud workspace. Returns run IDs, statuses, trigger reasons, and timestamps.
`terraform.terraform_get_run`	Read	runId	Get details of a specific Terraform Cloud run by its ID. Returns run status, plan/apply results, and configuration version info.
`terraform.terraform_list_variables`	Read	workspaceId	List variables for a Terraform Cloud workspace. Returns variable names, types (Terraform or environment), and sensitivity flags.
`terraform.terraform_list_organizations`	Read	pageNumber, pageSize	List Terraform Cloud organizations the authenticated user has access to. Returns organization names and IDs.
`terraform.terraform_get_current_user`	Read	none	Get the currently authenticated Terraform Cloud user. Useful for verifying authentication and retrieving user details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Terraform Cloud CLI Pages

CI Terraform Cloud CLI for CI. Cron Jobs Terraform Cloud CLI for cron jobs. Shell Scripts Terraform Cloud CLI for shell scripts. Coding Agents Terraform Cloud CLI for coding agents.