Chef MCP Server

A head chef's verified answers as tools: scale recipes, fix cooking faults, swaps, yields and costs.

Local serverstdio

What is the Chef MCP Server?

Chef is an MCP integration. A head chef's verified answers as tools: scale recipes, fix cooking faults, swaps, yields and costs.

Packages and local setup

The published npm package is kitchen-pass-mcp, version 0.1.0. Its declared MCP transport is stdio.

The package declares KITCHEN_PASS_NETWORK (required): base (real USDC) or base-sepolia (test USDC); KITCHEN_PASS_PAYER_KEY_FILE: Absolute path to your own wallet key file (mode 600); without it the server only quotes; KITCHEN_PASS_MAX_SPEND_PER_SESSION: USD cap per session, default 0.10, at most 1; KITCHEN_PASS_MAX_SPEND_PER_DAY: USD cap per day, default 0.50, at most 5.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related cloud & devops MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
KITCHEN_PASS_NETWORKbase (real USDC) or base-sepolia (test USDC)Yes
KITCHEN_PASS_PAYER_KEY_FILEAbsolute path to your own wallet key file (mode 600); without it the server only quotesCheck documentation
KITCHEN_PASS_MAX_SPEND_PER_SESSIONUSD cap per session, default 0.10, at most 1Check documentation
KITCHEN_PASS_MAX_SPEND_PER_DAYUSD cap per day, default 0.50, at most 5Check documentation