Claude Code zerodust zerodust_register_api_key
How to: Claude Code zerodust zerodust_register_api_key
Add zerodust to Claude Code
-
01
Run this in your project directory.
claude mcp add --transport http zerodust https://api.zerodust.xyz/mcp-
02
Restart your session so the server is picked up.
-
03
Ask for something zerodust_register_api_key does. Claude Code lists the server's tools on connect and calls zerodust_register_api_key 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.
Adds it for this project only. Append --scope user to make it available everywhere. Claude Code docs
Set these first
zerodust will not start until these are set, so zerodust_register_api_key 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.