Skip to content

Windsurf Terradev agent_vector_db_up

How to: Windsurf Terradev agent_vector_db_up

client:Windsurf transport:sse tool:agent_vector_db_up

Add Terradev to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "terradev": {
      "serverUrl": "https://terradev-mcp.terradev.cloud/sse"
    }
  }
}
  1. 02

    Save the file and restart Windsurf.

  2. 03

    Ask for something agent_vector_db_up does. Windsurf lists the server's tools on connect and calls agent_vector_db_up itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Terradev's identifier in your config matches the one above exactly.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs

Set these first

Terradev will not start until these are set, so agent_vector_db_up 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.