Agent-native

Use Strega from your AI assistant

Everything you can do on this site, your assistant can do too: same recipes, same scaling, same shopping lists.

Connect

Add Strega as a custom connector (remote MCP server) in Claude, ChatGPT, Grok, Cursor, VS Code, or Goose with this URL:

https://strega.food/mcp

Nothing to install and no API key. Clients that discover servers from a domain find it through the AI Catalog and its Server Card.

Adding the connector signs you in to Strega with Apple or Google, the same account as this site. Your allergies, diet and household size apply from the first search, and anything your assistant saves shows up in My Kitchen.

Your assistant can search, open recipes, guide you step by step, plan meals and build a shopping list before you sign in (public recipes, nothing saved). Saving, keeping a plan or list, ordering and anything that changes your kitchen asks you to sign in first. Recipe pages, llms.txt and the JSON and text versions of every recipe stay open without an account. To disconnect, remove the connector in your assistant. Strega only receives the tool calls your assistant makes, never your conversation. Privacy policy · Terms

Use Strega in Grok

Grok reaches Strega four ways. Each one uses the same URL.

grok.com

Open Connectors → New Connector → Custom, paste https://strega.food/mcp, and complete the sign-in (OAuth). Connectors in Grok

Grok Bot

Install Strega from Connect apps once it’s listed. Until then, ask your Bot to add a custom MCP server with https://strega.food/mcp.

Grok Build CLI

grok mcp add --transport http strega https://strega.food/mcp

MCP servers in Grok Build

xAI API

Pass Strega as a remote MCP tool:

{
  "type": "mcp",
  "server_url": "https://strega.food/mcp",
  "server_label": "strega",
  "allowed_tools": [
    "search_recipes",
    "get_recipe",
    "plan_meals",
    "build_shopping_list",
    "suggest_from_pantry",
    "get_cook_steps"
  ]
}

The xAI API takes only a static Authorization header, with no OAuth, so Strega runs signed out there (public tools only). Signed-in API use waits on personal API keys. Remote MCP in the xAI API

Tools

search_recipes

Find recipes by keywords, time, diet tags, and ingredients on hand or to avoid. The cook's own versions come first; mine: true shows only those.

get_recipe

A full recipe at any servings, US or metric (or the cook's own unit for an ingredient, like butter in grams), with amounts written into every step; the cook's own versions of it, and sound substitutions on request.

get_cook_steps

A gather list, then one step at a time with timers, for hands-free guidance.

plan_meals

Dinners for the coming days by day: varied, perishables first, one new to the cook, plus the merged shopping list.

update_meal_plan

Swap, drop or add a day in a saved plan ("swap Tuesday for something faster"); the same plan and list, recomputed.

build_shopping_list

Any set of recipes merged into one list by aisle, with what to buy.

update_shopping_list

After the cook says what they already have: take those off a saved list, move back anything they are out of, add extras. Lists set aside staples and small amounts of bulk items as likely_have (3 tbsp flour, not a 5 lb bag) and ask first; saving to the pantry is a separate ask.

pantry

What the cook has on hand: tell it in their own words ("2 lbs of chicken thighs, half an onion, we're out of eggs") and it returns exactly what changed; with nothing passed, the pantry and staples. Everything in it is left off shopping lists.

suggest_from_pantry

Recipes ranked by how much of each the cook already has, with what's missing named on every one. Works signed out with the list passed in.

draft_recipe

Turn a pasted recipe or a link into a draft for the cook to check before it's published. A recipe already on Strega (the same link, or the same recipe) comes back as existing instead of a copy. A site that only opens for its own readers comes back as blocked: pass the page's text with source_url if you can see it.

create_recipe

Publish a recipe from text, a photo of a card, or a conversation, or publish a confirmed draft.

fork_recipe

Save the cook's own version of a recipe, linked to the original, public or just for them; named after the change.

update_recipe

Change a recipe the cook owns, passing only what changes, or add the cook's own photo as the cover or on a step (photo: a link or the file as base64; never a generated or stock image). Every edit keeps a revision that can be restored.

rate_recipe

Post the cook's rating and comment, or update the one they already gave. A cook can't rate their own recipe.

save_recipe

Save a recipe to the cook's kitchen, or take it off (saved: false).

delete_recipe

Delete a recipe the cook owns, for good, when nobody else has made a version of it, reviewed it or saved it; otherwise it points at taking the recipe off Strega (update_recipe with unpublished), which can be undone.

get_my_kitchen

What the cook saved, published, changed, planned and rated, and which of their recipes need a better photo.

get_my_stats

How the cook's own recipes are doing: views, shares, prints, cooks, saves, versions and ratings, by day, per recipe and by region. Counts only, never who.

hand_back_recipe

Hand back a recipe the Strega team added to the cook's kitchen when it isn't theirs.

preferences

The cook's allergies, diet, household size, units and more; changes only after the cook confirms. Never infers allergies.

cook_profile

A cook's public page: name, about and links when they show them, and their public recipes; nothing private. Changes the cook's own only after they confirm.

report_content

Report a recipe, review, photo or profile to Strega's moderators, in the cook's words.

generate_placeholder_cover

Put a generated placeholder picture of the dish on the cook's own recipe until they add a photo. Labeled as an illustration; never replaces a real photo.

Prompts and resources

Five prompts are the same paths as one command your assistant can show you (as a slash command or a suggestion, depending on the assistant): plan_my_week, what_can_i_make, cook_with_me, add_my_recipe and make_it_my_way. Each is a short brief that runs the tools above in order, shows you the change before anything is saved, and asks one question at a time.

Resources let you attach a recipe the way you would a file: befana://recipe/<slug> is the recipe as JSON (the same as /<slug>.json; add ?servings=4&units=metric to scale it), befana://recipe/<slug>.txt is plain text, and befana://kitchen is My Kitchen once you’re signed in. Recipe slugs complete from titles as you type.

Other ways in

Open REST (OpenAPI 3.1 at /openapi.json: every route, who may call it and its MCP twin): /api/recipes?q=, /<slug>.json (format befana-recipe/0.1), /<slug>.txt, /api/cooks/<handle>. Signed in: POST /api/shopping-list, /api/favorites, /api/me, /api/me/profile, /api/preferences. Discovery: llms.txt, sitemap, schema.org Recipe data on every page.

Cooks adding their own recipes: the contributor guide covers what a Strega recipe needs, the photo standard and what “tested” means. create_recipe and update_recipe take tested: { minutes } only when the cook says they cooked it and how long it took.

From the cook’s own device: POST /api/recipes/handoff takes a recipe page the cook has open, with no session (its link plus a PDF or photo of it, its schema.org Recipe JSON-LD, or its text) and answers with a link to /new?handoff=<code> that works for 15 minutes. That’s how sites that only open for their readers get into Strega: the page comes from the cook’s browser, never fetched by our servers. On Android, the installed app is in the share menu. On a computer, drag this to the bookmarks bar and click it on a recipe page:

Add to StregaDrag it to your bookmarks bar. On a recipe page, click it and the recipe comes here.

On a phone: strega.food/app installs Strega on the home screen. It’s the link to give a cook who wants the recipes without an assistant; a recipe’s own link works too.