VS Code pusaka pusaka_audit
How to: VS Code pusaka pusaka_audit
Add pusaka to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"pusaka": {
"type": "http",
"url": "https://pusaka-two.vercel.app/api/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something pusaka_audit does. VS Code lists the server's tools on connect and calls pusaka_audit itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that pusaka's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Set these first
pusaka will not start until these are set, so pusaka_audit never becomes available.
-
PUSAKA_ACCOUNT_ID -
PUSAKA_PRIVATE_KEY -
PUSAKA_MAX_SPEND_NEAR -
PUSAKA_CONTRACT -
PUSAKA_ALLOW_OUTFLOWS -
PUSAKA_ALLOWED_RECIPIENTS -
PUSAKA_CONFIRM
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.