smeet666/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 Desktop, Cursor, and any client using the standard config format**
Node 24 or later is required, and no environment variable has to be set.
With Docker
-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.1.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
| Tool | What it does |
| ------------------- | ------------------------------------------------------------------ |
| get_recipe | Reads one page of the recipe section, rescaled on request. |
| search_recipes | Finds recipes by dish or by ingredient. |
| list_facets | Lists the values each taxonomy publishes. |
| browse_recipes | Reads one taxonomy, page by page. |
| scale_ingredients | Rescales any Spanish ingredient list, with no request to the site. |
get_recipe
Reads one page of the recipe section, and rescales its quantities when a number
of servings is given.
| Argument | Type | Required | What it does |
| ---------- | --------------------------- | -------- | ---------------------------------------------------- |
| id | string, 1 to 200 characters | yes | The slug in a recipe's address, as a row carries it. |
| servings | integer, 1 to 1000 | no | Rescale the quantities to this many. |
**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.
| Argument | Type | Required | What it does |
| -------- | --------------------------- | -------- | ------------------------------------ |
| query | string, 1 to 120 characters | yes | A dish or an ingredient, in Spanish. |
| limit | integer, 1 to 60 | no | Rows to return. |
**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