Terrakube MCP Server

Terrakube Model Context Protocol Server

Local serverstdioTypeScript

What is the Terrakube MCP server?

Terrakube MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Terrakube Model Context Protocol Server.

What you get

A Model Context Protocol (MCP) server for Terrakube operations, enabling workspace management, variable handling, module operations, and organization management.

  • Comprehensive API Integration — Full integration with Terrakube's API for seamless operations
  • Type Safety — Built with TypeScript for enhanced type safety and developer experience
  • Error Handling — Robust error handling with clear error messages
  • Environment Configuration — Flexible configuration through environment variables
  • Modular Design — Organized code structure for easy maintenance and extension

Setting it up

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Terrakube is connected, these are the calls the assistant has available:

  • Workspaces — The Workspaces tool exposed by this server
  • createWorkspace — Create a new workspace in Terrakube. - Inputs: - name (string): Name of the workspace - organization (string): Organization name - description
  • updateWorkspace — Update an existing workspace. - Inputs: - name (string): Name of the workspace - organization (string): Organization name - description (optional
  • deleteWorkspace — Delete a workspace. - Inputs: - name (string): Name of the workspace - organization (string): Organization name - Returns: Success status
  • getWorkspace — Get details of a specific workspace. - Inputs: - name (string): Name of the workspace - organization (string): Organization name - Returns
  • listWorkspaces — List all workspaces in an organization. - Inputs: - organization (string): Organization name - Returns: Array of workspace details
  • Variables — The Variables tool exposed by this server
  • createVariable — Create a new variable in a workspace. - Inputs: - name (string): Name of the variable - organization (string): Organization name - workspace
  • updateVariable — Update an existing variable. - Inputs: - name (string): Name of the variable - organization (string): Organization name - workspace (string)
  • deleteVariable — Delete a variable. - Inputs: - name (string): Name of the variable - organization (string): Organization name - workspace (string): Workspace
  • getVariable — Get details of a specific variable. - Inputs: - name (string): Name of the variable - organization (string): Organization name - workspace
  • listVariables — List all variables in a workspace. - Inputs: - organization (string): Organization name - workspace (string): Workspace name - Returns: Array

Configuration and credentials

You will need 4 environment variables: TERRAKUBE_API_URL, TERRAKUBE_PAT_TOKEN, YOUR_API_URL, YOUR_PAT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Terrakube.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the terrakube mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Terrakube's toolset — Workspaces, createWorkspace, updateWorkspace and 11 more — is a fair guide to whether it matches your workflow. It is maintained by AzBuilder; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
WorkspacesThe Workspaces tool exposed by this server.
createWorkspaceCreate a new workspace in Terrakube. - **Inputs**: - name (string): Name of the workspace - organization (string): Organization name - description (optional string): Workspace description - vcsProviderId (optional string
updateWorkspaceUpdate an existing workspace. - **Inputs**: - name (string): Name of the workspace - organization (string): Organization name - description (optional string): New workspace description - vcsProviderId (optional string):
deleteWorkspaceDelete a workspace. - **Inputs**: - name (string): Name of the workspace - organization (string): Organization name - **Returns**: Success status
getWorkspaceGet details of a specific workspace. - **Inputs**: - name (string): Name of the workspace - organization (string): Organization name - **Returns**: Workspace details
listWorkspacesList all workspaces in an organization. - **Inputs**: - organization (string): Organization name - **Returns**: Array of workspace details
VariablesThe Variables tool exposed by this server.
createVariableCreate a new variable in a workspace. - **Inputs**: - name (string): Name of the variable - organization (string): Organization name - workspace (string): Workspace name - value (string): Variable value - description (op
updateVariableUpdate an existing variable. - **Inputs**: - name (string): Name of the variable - organization (string): Organization name - workspace (string): Workspace name - value (string): New variable value - description (optiona
deleteVariableDelete a variable. - **Inputs**: - name (string): Name of the variable - organization (string): Organization name - workspace (string): Workspace name - **Returns**: Success status
getVariableGet details of a specific variable. - **Inputs**: - name (string): Name of the variable - organization (string): Organization name - workspace (string): Workspace name - **Returns**: Variable details
listVariablesList all variables in a workspace. - **Inputs**: - organization (string): Organization name - workspace (string): Workspace name - **Returns**: Array of variable details
ModulesThe Modules tool exposed by this server.
createModuleCreate a new module. - **Inputs**: - name (string): Name of the module - organization (string): Organization name - provider (string): Module provider - description (optional string): Module description - **Returns**: Cr

How to install the Terrakube MCP server

{
  "mcpServers": {
    "server-terrakube": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "TERRAKUBE_API_URL": "your-value",
        "TERRAKUBE_PAT_TOKEN": "your-value",
        "YOUR_API_URL": "your-value",
        "YOUR_PAT_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
TERRAKUBE_API_URLEndpoint or connection string the server talks to.Yes
TERRAKUBE_PAT_TOKENCredential the server authenticates with.Yes
YOUR_API_URLEndpoint or connection string the server talks to.Yes
YOUR_PAT_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Terrakube to Workspaces.
  • Use Terrakube to createWorkspace.
  • Use Terrakube to updateWorkspace.

Frequently asked questions

It connects Terrakube to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Workspaces, createWorkspace, updateWorkspace, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Terrakube directly.