Zed zerodust zerodust_get_chains
How to: Zed zerodust zerodust_get_chains
Add zerodust to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"zerodust": {
"url": "https://api.zerodust.xyz/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something zerodust_get_chains does. Zed lists the server's tools on connect and calls zerodust_get_chains itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that zerodust'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
zerodust will not start until these are set, so zerodust_get_chains never becomes available.
-
ZERODUST_API_URL -
ZERODUST_API_KEY -
ZERODUST_ALLOW_EXECUTE -
ZERODUST_SIGNER_MODULE -
ZERODUST_KEYSTORE_FILE -
ZERODUST_KEYSTORE_PASSWORD_FILE -
ZERODUST_KEYSTORE_PASSWORD -
ZERODUST_PRIVATE_KEY_FILE -
ZERODUST_PRIVATE_KEY -
ZERODUST_ALLOWED_DESTINATIONS
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.