Cookbook MCP Server

Cookbook MCP server exists for a simple reason — assistants are far more useful when they can act on Cookbook directly instead of describing what you should do. 一个菜谱mcp server.

What you get

4. 如果使用sse server，需要进行一下修改 - cookbook.py中修改执行入口 python if __name__ == "__main__": # Initialize and run the server mcp.run(transport='sse') - mcp client配置修改。注意端口号。 json { "mcpServers": { "cookbook": { "url": "http://localhost:PORT/sse" } } }

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need one environment variable: COOKBOOK_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by ZXreaper; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cookbook's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cookbook mcp server does with a few real requests.