Claude, save this recipe.

The recipes that matter most were never written down properly. They live on folded index cards, in the margins of church cookbooks, and in someone's memory. We built Old Family Recipe to stop them from getting lost. (We've written about why family recipes matter and the one thing most people forget when saving them — the short version is: the story is what disappears first.)

Until today, you still had to open the app and type them in yourself.

Not anymore. If you're using any MCP-compatible AI client — Claude Desktop, Cursor, Claude Code, Cline, Windsurf, or similar — you can hand it a photograph of grandma's handwritten recipe card and say "save this to my cookbook." Your AI reads the handwriting, extracts the ingredients and steps, attaches the card photo, and files it under whoever made it. No app switching. No typing it in twice.

What shipped today

- 14 MCP tools covering the full cookbook surface — save recipes from handwritten cards, plan your week with Sage, generate shopping lists, invite family, and more - The `recipe://` protocol — every recipe gets a stable URI like `recipe://Grandmas-Thanksgiving-Stuffing` that any AI agent can reference - Self-serve API keys at /settings/developer — create, name, and revoke in seconds. No waitlist. - Protocol spec — the full reference, free to read, free to build against

Start using it

1. Get an API key. Free tier includes 100 API calls a month. 2. Paste six lines of config into your MCP client of choice. 3. Ask it to save a recipe.

The recipes that matter most are still the ones grandma made. Now your AI can help you keep them.

Not a developer? You can still photograph a handwritten recipe card and watch it become a saved recipe in 30 seconds — no AI client or API key needed. Try the camera demo → (no signup required to try) or create a free account to start your family's living cookbook. Print it as a softcover, hardcover, or heirloom cookbook when you're ready.