Cline Terradev hf_smart_template
How to: Cline Terradev hf_smart_template
Add Terradev to Cline
-
01
Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_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 Cline.
-
03
Ask for something hf_smart_template does. Cline lists the server's tools on connect and calls hf_smart_template 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.
Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs
Set these first
Terradev will not start until these are set, so hf_smart_template 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.