cookbook-mcp-server

What is cookbook-mcp-server?

It is an MCP server that provides access to a collection of recipes from the HowToCook GitHub repository. It offers tools to list all dishes and retrieve individual cooking instructions, intended for use with MCP clients like AI coding assistants or IDEs.

How to use cookbook-mcp-server?

Clone the HowToCook repository and set the COOKBOOK_URL constant in cookbook.py to the local dishes folder path. Configure your MCP client with the correct uv command and script path, or switch to SSE transport by modifying the server entry point and client URL settings.

Key features of cookbook-mcp-server

• get_all_dishes: retrieve all dish names from the cookbook
• get_recipe: retrieve a detailed recipe for a specific dish
• Supports both stdio and SSE transport modes
• Uses uv for dependency and environment management
• Easily integrates with MCP clients such as Cursor

Use cases of cookbook-mcp-server

• Querying recipe lists via an AI coding assistant
• Getting step-by-step cooking instructions on demand
• Embedding cookbook data into chat interfaces or IDEs

FAQ from cookbook-mcp-server

What tools does cookbook-mcp-server provide?

It provides get_all_dishes to list all dishes and get_recipe to retrieve a specific recipe.

What dependencies are required to run the server?

You need uv installed, and you must clone the HowToCook repository (dishes folder) to supply the cookbook data.

How do I switch between stdio and SSE transport?

By default the server uses stdio. To use SSE, change the mcp.run() call to mcp.run(transport='sse') and update the client configuration to use an url endpoint with the appropriate port.

Where does the cookbook data come from?

The data comes from the GitHub repository https://github.com/Anduin2017/HowToCook/tree/master—specifically the dishes folder, which must be cloned locally.

Does the server support authentication or other transports?

The README only documents stdio and SSE; no authentication mechanism is mentioned.