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.
A Terrakube management client covering 16 tools over organizations, workspaces, private-registry modules and workspace variables.
- 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.
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.
One command plus a key — npx -y @smithery/cli install @AzBuilder/mcp-server-terrakube --client claude, then supply credentials