How to digitise a physical cookbook with AI (without retyping a thing)

Most cookbooks live in the wrong format. They're beautiful objects on the shelf, but the moment you actually want to cookfrom one, you need three hands: one for the book, one for the spoon, one to flip back and forth between the ingredient list and the method. Anyone who's ever propped a hardback open with a tin of tomatoes knows the problem.

Until recently, the fix involved either retyping the recipe yourself (slow, boring) or paying a recipe app to scan it and inevitably mangle the quantities (fast, infuriating). The arrival of multimodal AI plus MCP changed that. You can now photograph a cookbook page and have your existing AI assistant — Claude or ChatGPT — turn it into a structured, interactive recipe card in about 30 seconds, for free, without leaving the chat.

Here's the practical how-to. We'll use Surprise Chef AI, the free MCP app we built for exactly this kind of thing, but the same technique works with any kitchen-aware MCP server.

What you'll need

• A phone, tablet, or laptop with a camera (or any way to upload an image)
• A cookbook, recipe card, magazine clipping, or hand-written family recipe
• An AI client that supports MCP — Claude, ChatGPT, or anything else MCP-aware
• A free Surprise Chef account connected to that AI

Setup time: about three minutes if it's your first time, then it's zero from then on.

Step 1: Take the photo properly

Most failures at this step are lighting failures. The AI is good but it's not magic — give it a fighting chance:

• Flat the page.Hold the book open or weight the corners so the spine doesn't curve the text. A curved page introduces perspective distortion that AIs struggle with.
• Even, indirect light. Window light from the side is ideal. Avoid direct sun (creates harsh shadows) and overhead kitchen spots (yellow cast).
• Fill the frame. Get close enough that the recipe fills most of the photo. Avoid including the opposite page if you can — it gives the AI two recipes to confuse.
• One photo, not three. If the recipe runs across two pages, take one wide photo of both. The AI handles a single wide image far better than two separate ones it has to stitch together.

For handwritten recipes, the same rules apply, but slow down — give the AI a sharper, larger image. We'll come back to handwriting in a moment.

Step 2: The prompt

Open your AI client (Claude, ChatGPT, etc.) with Surprise Chef connected, attach the photo, and paste this:

Here's a photo of a cookbook page. Save it as a smart recipe — pull out the ingredients, structure the steps with mise en place and parallel cooking tracks, and add timers wherever there's a duration mentioned. Keep the original wording in the notes field.

Three things matter about that prompt:

1. "Save it as a smart recipe"tells the AI to call Surprise Chef's save_recipetool, not just summarise the page back at you. This is the difference between "the AI showed me a recipe" and "the recipe is now in my kitchen forever."
2. "Mise en place and parallel tracks"nudges the AI to think about the structure before just dumping the steps in order. Good cookbooks already imply this — "while the onions caramelise, prepare the…" is two parallel tracks. Surprise Chef renders these as side-by-side columns in the smart card.
3. "Keep the original wording in the notes" preserves the author's voice. This matters more than you'd think — "a generous knob of butter" is information that gets lost the moment some AI helpfully "normalises" it to "30g butter."

Hit send. The AI will spend 10–30 seconds reading the photo, calling the tool, and saving the result. You'll see a confirmation in the chat and the recipe will appear in your dashboard immediately.

Step 3: Sanity-check the result

AI vision is good, not perfect. Open the new recipe in your dashboard (or just ask the AI to show it to you in chat) and skim it once. Things worth checking:

• Quantities for ambiguous units."1 cup" is unambiguous. "1 small handful" is not — make sure the AI didn't silently convert it to a precise number. If it did, the number is a guess.
• Servings count.Cookbooks aren't always explicit about this. The AI will infer one if it can't see it. Check it matches your read of the recipe.
• Whether anything got dropped. Garnishes, optional ingredients, and footnotes are the usual casualties. A 10-second skim catches them.

If you spot anything wrong, just ask the AI to fix it: "The servings should be 6, not 4 — update the recipe." Surprise Chef will call its update_recipe tool and the change is live.

Special cases

Handwritten recipes (grandma's cards)

These are the most emotionally important and the most technically annoying. They're also the reason we built this feature in the first place.

Prompt tweak: tell the AI it's handwritten, so it slows down on the OCR step.

Here's a photo of my grandma's handwritten recipe card. Save it as a smart recipe. Take your time on the handwriting. Keep her exact wording in the notes — that's the part I care about.

Then check the result twice. Old recipe cards often use abbreviations like "tsp", "T" (capital for tablespoon), or "pt" for pint. The AI usually gets these right but it's worth a glance. And the wording — "cook till done", "a knob of butter the size of a walnut" — should survive untouched in the notes.

Magazine clippings and online recipes

For magazines, the same approach works. For URLs, you can skip the photo entirely and just paste the link:

Here's a recipe URL: [paste]. Save it as a smart recipe in my kitchen. Strip the SEO blog content — I just want the actual recipe.

That last instruction is the most important one. Modern recipe sites bury a 300-word recipe in 2,000 words of personal essay for SEO reasons. The AI will happily filter that out if you ask. Yours is a clean ingredient list and method, none of the "my grandmother taught me in Tuscany" preamble.

Bulk-importing a whole cookbook

If you're sitting down with one favourite cookbook and want to digitise the whole thing, do it one recipe at a time, not in a batch. Reasons: you'll catch errors as you go, your AI client's rate limits won't bite, and you'll naturally start tagging them properly ("weeknight", "dinner-party", "Matteo loves this") which makes them findable later.

Realistic pace: about 1 minute per recipe including the sanity-check skim. A 50-recipe cookbook is an hour's work, spread over an evening or two.

What you get on the other side

Once a recipe is in Surprise Chef, it stops being a static page and becomes something genuinely useful in the kitchen:

• Smart card layout — mise en place at the top, parallel cooking tracks side-by-side, finish steps at the bottom. No more flipping between ingredients and method.
• Built-in timers — every step that mentions a duration gets a tap-to-start timer. The card stays visible while it counts down.
• Searchable— "find me a recipe like that lasagne from grandma's book" just works, even months later.
• Plannable— drop it into next week's meal plan and Surprise Chef adds the missing ingredients to your shopping list automatically.
• Yours, forever — the data lives on your account, not in a chat thread that gets summarised away. Switch from Claude to ChatGPT next year and the recipe is still there.

The wider point

For decades, "digitising a cookbook" meant "retyping it into a notes app where it slowly rotted." Now it's a 30-second photo and a sentence to your AI. The bottleneck has moved from the typing to the deciding-which-recipes-are-worth-keeping. Which is a much better problem to have.

If you've got a stack of cookbooks staring at you from a shelf and a bunch of grandma's recipe cards in a drawer, this is the moment.Sign up free, connect it to your AI, and you can start tonight.