Terrakube MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TERRAKUBE_API_URL | Yes | Your Terrakube API URL | |
| TERRAKUBE_PAT_TOKEN | Yes | Your Terrakube personal access token | |
| TERRAKUBE_ORGANIZATION | Yes | Your Terrakube organization name |
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 |
|---|---|
| list-organizationsB | Lists all organizations accessible to the current user |
| get-organizationB | Retrieves detailed information about a specific organization by its ID |
| create-organizationC | Creates a new organization with the specified name and optional description |
| edit-organizationC | Updates an existing organization's details |
| list-workspacesC | Lists all workspaces in the specified organization |
| get-workspaceC | Retrieves detailed information about a specific workspace |
| create-workspaceC | Creates a new workspace in the specified organization |
| edit-workspaceC | Updates an existing workspace's details |
| list-modulesB | Lists all modules in the specified organization |
| get-moduleC | Retrieves detailed information about a specific module |
| create-moduleC | Creates a new module in the specified organization |
| edit-moduleC | Updates an existing module's details |
| list-variablesB | Lists all variables in the specified workspace |
| get-variableC | Retrieves detailed information about a specific variable |
| create-variableC | Creates a new variable in the specified workspace |
| edit-variableC | Updates an existing variable's details |
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 16 tools
Every tool has a clearly distinct purpose with no ambiguity, as each combines a specific action (create, edit, get, list) with a specific resource type (module, organization, variable, workspace). The descriptions reinforce this clarity, making misselection unlikely.
Tool names follow a perfectly consistent verb-noun pattern throughout, using hyphen-separated lowercase (e.g., create-module, edit-organization). All tools adhere to this convention without any deviations or mixed styles.
With 16 tools, the count is well-scoped for managing Terraform-like resources (modules, organizations, variables, workspaces). Each tool earns its place by covering CRUD operations across four resource types, avoiding bloat or thinness.
The tool set provides complete CRUD/lifecycle coverage for the inferred domain of infrastructure management, with create, edit, get, and list operations for all four resource types. There are no obvious gaps or dead ends in the surface.