Gemini CLI Terradev agent_langgraph_deploy

How to: Gemini CLI Terradev agent_langgraph_deploy

client:Gemini CLI transport:sse tool:agent_langgraph_deploy

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
Ask for something agent_langgraph_deploy does. Gemini CLI lists the server's tools on connect and calls agent_langgraph_deploy itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Terradev's identifier in your config matches the one above exactly.

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 agent_langgraph_deploy never becomes available.

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 tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Terradev MCP server