Skip to main content
A local MCP server and the sauce command share wallet files and Pot records. By default, each sees the wallets and Pots created by the other. The HTTP server has no wallet or Pot store. On start, the server names both stores on stderr:
Wallets over stdio covers the wallet directory and its tools.

​
The Pot store

A Pot is the account a cook runs on (Pot). The store records every Pot a transaction sent by this server deploys, once the chain shows it. That covers a deployment sent through sauce_send or sauce_wallet_send. The store’s files are the ones sauce pot list and sauce pot import read and write. Each record has:
  • the chain, address, owner, salt and kind;
  • the Kitchen;
  • the release the Pot was deployed under: release and engine;
  • deployment, the transaction that deployed it.
Use a record’s Kitchen and engine to identify the release that deployed its Pot. The store keeps the record; it does not move funds or change the Pot’s release.

​
sauce_pot_list

Lists the store. It reads no chain. chain and owner filter the list.
sauce_pot reports what a Pot holds now.

​
sauce_pot_import

Records a Pot that this machine did not deploy, read from the chain:
  • { chain, pot } on an EVM chain: the owner, salt and Kitchen are read from the Pot.
  • { chain, owner, salt } or { chain, owner, saltHex }: every known release’s Pot of that owner and salt that has code is recorded. On Solana this is the only form, because a Solana Pot names no owner.
A Pot already in the store keeps its record. The result is store and pots, as sauce_pot_list gives them.

​
Configure storage

With --no-stores the server writes no wallet or Pot records. A send’s result still carries pots, the record of each Pot it deployed, for the client to keep. The HTTP server refuses the store flags at start:

​
Next steps