Kitchen Pass MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KITCHEN_PASS_CONFIRM | No | Payment confirmation mode: `elicit` (ask where the host supports it) or `off`. | elicit |
| KITCHEN_PASS_DRY_RUN | No | Set to `1` to make the server quotes only. | |
| KITCHEN_PASS_NETWORK | Yes | The network to use: `base` (real USDC) or `base-sepolia` (test USDC). Required; if missing or wrong, every tool reports it. | |
| KITCHEN_PASS_LEDGER_DIR | No | Absolute path of the folder for the spend ledgers, one per network; a leading `~/` is expanded. | ~/.kitchen-pass-mcp |
| KITCHEN_PASS_PAYER_KEY_FILE | No | Absolute path to your key file (mode 600); a leading `~/` is expanded. Unset means the server only quotes and does not pay. | |
| KITCHEN_PASS_MAX_SPEND_PER_DAY | No | USD spend cap per UTC day, e.g. `0.50` (at most `20`). A cap that isn't a plain amount like `0.50`, or is over the ceiling, turns paying off. | 0.50 |
| KITCHEN_PASS_MAX_SPEND_PER_SESSION | No | USD spend cap per session, e.g. `0.10` (at most `5`). A cap that isn't a plain amount like `0.50`, or is over the ceiling, turns paying off. | 0.10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues