create-module
Creates a new module in the specified organization
LABSCO SUMMARY
Every object here can be created and edited and none of them can be deleted, which settles what an agent may safely be left alone with.
Organizations, workspaces, modules and variables all follow the same list, get, create and edit shape, with no delete tool anywhere in the set, so an unattended call can add or change but not remove. Variables are the one place values you would not want echoed pass through: create-variable and edit-variable both take a sensitive flag alongside the value. Workspaces bind to version control at creation rather than afterwards — vcsProvider and vcsRepo are parameters on create-workspace.
What it is
A Terrakube management client covering 16 tools over organizations, workspaces, private-registry modules and workspace variables.
What you get
- Organizations: list-organizations for everything the token reaches, plus get-organization, create-organization and edit-organization.
- Workspaces inside an organization, created and edited with a terraformVersion, a vcsProvider and a vcsRepo.
- Private registry modules through list-modules, get-module, create-module and edit-module, each carrying a provider and a registry.
- Workspace variables with a key, a value, a category and a sensitive flag, through list-variables, get-variable, create-variable and edit-variable.
Requirements
TERRAKUBE_API_URL for the Terrakube instance and TERRAKUBE_PAT_TOKEN, a personal access token on it. Everything below organization level is addressed by organizationId, and variables additionally by workspaceId.
Setup effort
Add the configuration to your client
USE CASES
01
Standing up a workspace against a repository
A workspace is created inside a named organization with its Terraform version and its VCS provider and repository set at the same time, so it comes into existence already bound to code.
02
Setting the variables a workspace runs with
Variables belong to a workspace and carry a category alongside their value, with a sensitive flag deciding whether the value is treated as a secret.
03
Publishing a module into the organization's registry
Modules are registered against a provider and a registry inside an organization, so a shared module gets an entry other workspaces can reference rather than being copied around.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create-organization
Creates a new organization with the specified name and optional description
create-variable
Creates a new variable in the specified workspace
create-workspace
Creates a new workspace in the specified organization
edit-module
Updates an existing module's details
edit-organization
Updates an existing organization's details
edit-variable
Updates an existing variable's details
edit-workspace
Updates an existing workspace's details
get-module
Retrieves detailed information about a specific module
get-organization
Retrieves detailed information about a specific organization by its ID
get-variable
Retrieves detailed information about a specific variable
get-workspace
Retrieves detailed information about a specific workspace
list-modules
Lists all modules in the specified organization
list-organizations
Lists all organizations accessible to the current user
list-variables
Lists all variables in the specified workspace
list-workspaces
Lists all workspaces in the specified organization
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. Tool names use kebab-case create-, edit-, get- and list- forms, not the documented camelCase. The published package has no delete tools, and update is spelled edit.
Requires
- npx on PATH
- TERRAKUBE_PAT_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"terrakube": {
"command": "npx",
"args": [
"-y",
"@terrakube/mcp-server"
],
"env": {
"TERRAKUBE_API_URL": "<YOUR_API_URL>",
"TERRAKUBE_PAT_TOKEN": "<YOUR_PAT_TOKEN>"
}
}
}
}
