MCP Pequerecetas

mcp-pequerecetas

Pequerecetas is a Spanish home-cooking site written for families. It holds a few thousand recipes with their ingredients, their steps and their photographs, and files each one under the diet it suits, the appliance it is cooked in, the occasion it is made for and the age of whoever eats it, from six months up.

This server connects a chat client to that site. You can search its recipes, read one with its quantities rescaled to the number of people at your table, list the values each taxonomy publishes, walk a taxonomy page by page, and rescale any Spanish ingredient list you already hold. It needs no API key and no account.

_Version française_

Install

One-click install

Claude Code

claude mcp add pequerecetas -- npx -y mcp-pequerecetas

Claude Desktop, Cursor, and any client using the standard config format

{

"mcpServers": { "pequerecetas": { "command": "npx", "args": ["-y", "mcp-pequerecetas"] } } }

Node 24 or later is required, and no environment variable has to be set.

With Docker

{

"mcpServers": { "pequerecetas": { "command": "docker", "args": ["run", "-i", "--rm", "ghcr.io/smeet666/mcp-pequerecetas:1.2.0"] } } }

-i keeps stdin open, which is where the protocol travels, and -t is left out because a TTY rewrites the stream. The container needs outbound HTTPS to www.pequerecetas.com, and nothing else: no volume, no port, no credential.

Bundle, without npm

Download mcp-pequerecetas-1.2.0.mcpb from the latest release and open it. A client that supports MCP bundles installs it on its own, with no npm and no configuration file to edit. The bundle carries its dependencies, so nothing is fetched at install time.

What you can ask

• « Búscame una receta de paella de marisco. »
• "Read me that recipe for eight people."
• "What can I cook in an air fryer on this site?"
• "Show me the purées it files under six months."
• "Scale this Spanish ingredient list by three."

Pequerecetas is written in Spanish and its search matches the words a page was written with, so recipes are found in Spanish. The ordinary path runs from a search or a taxonomy to a recipe: a row carries an id, and get_recipe takes that id.

Tools

get_recipe

Reads one page of the recipe section, and rescales its quantities when a number of servings is given.

In return: kind, which reads recipe or collection. The site publishes both at this kind of address and describes them alike, so this is what tells them apart: a collection is an article gathering other recipes, and it comes back with headings and recipes, the rows it points at, in place of a recipe's fields.

A recipe carries source_shape, reading structured when the block the page publishes for search engines held its ingredients and article when they were read from the body of the page, which is where most of this site's recipes keep them. Then come title, url, description, published_at, modified_at, prep_minutes, cook_minutes, total_minutes, categories, cuisines, keywords, author, author_url, rating, nutrition and images, each null or empty where the page states nothing. yield says what the recipe was written for and what it was rescaled to; a page stating no number of servings comes back with factor at 1 and a note saying why. Each line of ingredients carries scaling, reading scaled, rounded or unscaled, and is_equipment, which marks a line naming a tool rather than something eaten.

search_recipes

Searches the recipes for a dish or an ingredient.

In return: rows carrying id, which get_recipe takes, title, url and image_url. Alongside come result_count for the rows returned and total_available, which is always null: the site publishes no count of what a search matched. The site serves its search on a single page and answers a request for a second with the first again, so these are all the rows it offers for a query. Some rows are articles gathering recipes, which get_recipe reports as a collection.

list_facets

Lists the values the site browses its recipes by, read from the sitemap each taxonomy publishes.

The taxonomies are dieta, edad, ingrediente, ocasion, recetas-de, tecnica, tipo-de-cocina and tipo-plato: diet, the age of whoever eats it, main ingredient, occasion, moment of the day, appliance, cuisine and kind of dish.

In return: facets, each carrying name, value_count and values, whose value is the slug browse_recipes takes. The values keep the order the site publishes them in. Reading all eight costs one request per taxonomy. A taxonomy that could not be read is named in notes and left out of facets, so a listing short of one never reads like a site that has seven.

browse_recipes

Reads one page of a taxonomy's recipes.

In return: rows of the same shape search_recipes returns, with page_served for the page the site actually served, has_more for whether its own pagination offers another, and total_available, always null because the site prints no count on these pages. The site writes its own slugs, so one built by hand reaches a page it does not hold and comes back as not_found. The taxonomies cannot be combined: the site offers no way to ask for two at once.

scale_ingredients

Rescales a list of Spanish ingredient lines. It reaches no site.

Give factor, or from_servings and to_servings together. Naming both ways at once is refused, because they can ask for different things.

In return: each line with text as it now reads, original as it was given, amount, amount_max, unit, and scaling, which carries the honesty of the answer: scaled when the arithmetic landed exactly, rounded when the value moved to stay something a kitchen can measure out, unscaled when the line carries no quantity. is_equipment marks a line naming a tool. Alongside come scaled_count, rounded_count and unscaled_count. Nothing is converted between unit systems, and an approximate measure such as a pizca keeps the size the cook gives it.

Configuration

| PQR_CACHE_MAX_ENTRIES | 200 | 1 to 5000 | Reads held at once.