Claude Code Terradev governance_move_data
How to: Claude Code Terradev governance_move_data
Add Terradev to Claude Code
-
01
Run this in your project directory.
claude mcp add --transport sse terradev https://terradev-mcp.terradev.cloud/sse-
02
Restart your session so the server is picked up.
-
03
Ask for something governance_move_data does. Claude Code lists the server's tools on connect and calls governance_move_data 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.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Set these first
Terradev will not start until these are set, so governance_move_data 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.