Skip to content

Cursor Terradev mlflow_list_experiments

How to: Cursor Terradev mlflow_list_experiments

client:Cursor transport:sse tool:mlflow_list_experiments

Add Terradev to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

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

    Save the file and restart Cursor.

  2. 03

    Ask for something mlflow_list_experiments does. Cursor lists the server's tools on connect and calls mlflow_list_experiments 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.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

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