Terradev MCP Server

What the code does

We read the source, 6 d ago · tools taken from the live server · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

            proc = subprocess.run(cmd, env=run_env, capture_output=True, text=True)

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    dd_cmd = f"dd if=/dev/zero of={test_file} bs=1M count=256 oflag=direct 2>&1; rm -f {test_file}"

                    "http://169.254.169.254/latest/meta-data/spot/termination-time",

            result = subprocess.run(

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

        proc = subprocess.Popen(

        return os.path.join(self.config.manifest_dir, f"{self.config.cycle_id}.json")

        env = {**dict(os.environ), **self.env}

              mountPath: /var/run/docker.sock

        ssh_key_path = os.path.expanduser("~/.ssh/id_rsa.pub")

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 25%

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

claude mcp add terradev --transport http https://terradev-mcp.terradev.cloud/sse

{
  "mcpServers": {
    "terradev": {
      "url": "https://terradev-mcp.terradev.cloud/sse"
    }
  }
}

[mcp_servers.terradev]
url = "https://terradev-mcp.terradev.cloud/sse"

{
  "mcpServers": {
    "terradev": {
      "url": "https://terradev-mcp.terradev.cloud/sse"
    }
  }
}

{
  "mcpServers": {
    "terradev": {
      "url": "https://terradev-mcp.terradev.cloud/sse"
    }
  }
}

This one needs environment variables set before it will start: RUNPOD_API_KEY (RunPod API key — get at runpod.io/console/settings/api-keys), VAST_API_KEY (Vast.ai API key — get at console.vast.ai/api-keys), LAMBDA_API_KEY (Lambda Labs API key — get at cloud.lambdalabs.com/api-keys), HF_TOKEN (HuggingFace API token — get at huggingface.co/settings/tokens), AWS_ACCESS_KEY_ID (AWS access key ID (pair with AWS_SECRET_ACCESS_KEY)), AWS_SECRET_ACCESS_KEY (AWS secret access key), GOOGLE_APPLICATION_CREDENTIALS (Path to GCP service account JSON key file), TERRADEV_MCP_BEARER_TOKEN (Bearer token for SSE/remote transport mode (stdio mode does not require this)). The author declared them in the registry entry; get the values from the project itself.

Available tools 245

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints