Skip to content

Zed Terradev query_database

How to: Zed Terradev query_database

client:Zed transport:sse tool:query_database

Add Terradev to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

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

    Save the file and restart Zed.

  2. 03

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

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

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