> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Local server storage

> What a Sauce MCP server started over stdio stores on disk, and how to move those stores or keep none.

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.

| Store | Default directory | Flag | Tools |
| - | - | - | - |
| Wallets | `~/.sauce/wallets` | `--wallets <dir>` | the six `sauce_wallet_*` tools |
| Pots | `~/.sauce/pots` | `--pots <dir>` | `sauce_pot_list`, `sauce_pot_import` |

On start, the server names both stores on stderr:

```text theme={null}
sauce mcp: serving the wallets in ./wallets; sauce_wallet_enable enables them to sign
sauce mcp: keeping the Pots its transactions deploy in ./pots
```

[Wallets over stdio](https://docs.eco.com/sauce-sdk/mcp/wallets.md) covers the wallet directory and its tools.

## The Pot store

A Pot is the account a cook runs on ([Pot](https://docs.eco.com/sauce/pot.md)). 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.

```json theme={null}
{ "store": "./pots", "pots": [] }
```

`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

| Start the server with | Wallet tools | Pot store tools | Tools in all |
| - | - | - | - |
| `sauce mcp` | yes, `~/.sauce/wallets` | yes, `~/.sauce/pots` | 27 |
| `sauce mcp --wallets <dir> --pots <dir>` | yes, the given directory | yes, the given directory | 27 |
| `sauce mcp --no-wallets` | none | yes | 20 |
| `sauce mcp --no-stores` | none | none | 18 |

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:

```text theme={null}
sauce mcp: --pots is for stdio: the HTTP server keeps nothing
sauce mcp: --no-stores is for stdio: the HTTP server keeps nothing
```

## Next steps

* [Wallets over stdio](https://docs.eco.com/sauce-sdk/mcp/wallets.md)
* [MCP tools](https://docs.eco.com/sauce-sdk/mcp/tools.md#pot-store-tools-stdio-only)
* [`sauce pot`](https://docs.eco.com/sauce-sdk/cli/pot): `sauce pot list` and `sauce pot import` at a terminal
* [Self-hosting over HTTP](https://docs.eco.com/sauce-sdk/mcp/self-hosting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.