Gemini CLI Terradev Resource/Alerts

How to: Gemini CLI Terradev Alerts

client:Gemini CLI transport:sse resource:Alerts

Add Terradev to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

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

02
Save the file and restart Gemini CLI.
03
Alerts is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
04
If it does not appear, check that Terradev is connected and that you are looking at its resources rather than its tools.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Terradev will not start until these are set, so it never reaches Gemini CLI.

RUNPOD_API_KEY
VAST_API_KEY
LAMBDA_API_KEY
HF_TOKEN
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
GOOGLE_APPLICATION_CREDENTIALS
TERRADEV_MCP_BEARER_TOKEN

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.

Terradev MCP server