Claude.ai Terradev agent_agentic_serving_configure
How to: Claude.ai Terradev agent_agentic_serving_configure
Add Terradev to Claude.ai
-
01
Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.
https://terradev-mcp.terradev.cloud/sse-
02
Save the file and restart Claude.ai.
-
03
Ask for something agent_agentic_serving_configure does. Claude.ai lists the server's tools on connect and calls agent_agentic_serving_configure 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.
Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs
Set these first
Terradev will not start until these are set, so agent_agentic_serving_configure 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.