Grok Terradev ray_stop
How to: Grok Terradev ray_stop
Add Terradev to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"terradev": {
"type": "sse",
"url": "https://terradev-mcp.terradev.cloud/sse"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something ray_stop does. Grok lists the server's tools on connect and calls ray_stop 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.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
Terradev will not start until these are set, so ray_stop 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.