You can save a recipe from ChatGPT or Claude straight into Thoughts by asking for the final, standalone version and then saying “save it in my Recipes project”. The recipe lands on your iPhone as a clean, searchable thought — ingredients first, steps numbered — ready for the next time you cook it, instead of buried in a chat you will never reopen. This guide covers the one-time setup, the exact prompts, scaling and swaps, and how to organise recipes so weeknight-you can find them fast.
One-time setup (five minutes)
- In Thoughts on your iPhone, create a project called Recipes and turn on cloud sync for it. Only synced projects are reachable by your assistant.
- Connect your assistant once: follow the ChatGPT steps or the Claude steps using the server URL
https://thoughtsai.cc/mcp. - Test the round trip: ask the assistant to show your projects, and confirm Recipes appears.
That is the whole infrastructure. From now on, saving a recipe is one sentence at the end of a conversation. If Recipes does not appear, sync has not finished or you signed into the connector with a different account — the troubleshooting sections of the connection guides cover both.
Generate a recipe worth saving
The quality of the saved note is decided by the prompt. Give constraints up front — servings, time, equipment, what is in the fridge — and ask for a cookbook layout:
Give me a weeknight mushroom risotto for two, ready in 40 minutes, one pan. Format it as: title, one-line description, servings and time, ingredients with quantities, then numbered steps with timings.
Iterate in the chat until it is right. Swap the wine for stock, make it vegan, halve the chilli. Only when the version on screen is the one you would cook do you move to saving — there is no prize for archiving drafts. Our set of recipe prompts that save as clean notes has a dozen more briefs for scaling, substitutions and using up leftovers.
Save it with one sentence
Save that final recipe as a thought in my Recipes project in Thoughts, titled “Mushroom risotto — weeknight, for two”.
Naming the title yourself is a small act with a long payoff. Search in Thoughts matches titles and text literally, so “risotto” and “weeknight” in the title guarantee retrieval on a tired Tuesday. “Dinner idea” guarantees nothing.
Then open Thoughts and glance at the new thought. Fix anything the chat formatted oddly, and check quantities with fresh eyes — an assistant can present a wrong oven temperature very beautifully. If a save ever reports an error, check the app before asking again; creating a thought is not idempotent, so a blind retry can duplicate the recipe.
Add the shopping side at the same time
A recipe you cannot shop for is half a tool. While the conversation is warm, ask for the list too:
Now make the grocery list for that recipe — only what I need to buy, grouped by shop section, with quantities. Assume I have oil, salt, pepper and rice. Save the list as a separate thought called “Shop: mushroom risotto”.
Keeping the list as its own thought means it can be ticked through and deleted without touching the recipe you keep forever. The dedicated guide to grocery lists from ChatGPT to Thoughts goes deeper on grouping, quantities and merging several meals into one shop.
Variations without losing the original
Next month, in either assistant, you can build on the saved version instead of starting from zero:
Find my mushroom risotto thought in Recipes, read it in full, then adapt it for four people and a pressure cooker. Save the result as a new thought called “Mushroom risotto — pressure cooker, for four”.
Because ChatGPT and Claude read the same library, the assistant you happen to have open can do this. Keep the original untouched — variations are new thoughts with honest titles — and your cookbook grows the way real ones do: a trusted base and its descendants.
Organise so future-you actually cooks
One Recipes project is enough to start. When it passes a few dozen saves, the filing habits in organising saved recipes — consistent titles, a “Shop:” prefix for lists, splitting Baking or Batch cooking only when browsing gets slow — keep it browsable. Resist a project per cuisine on day one; structure should follow use, the same principle as organising notes by project generally.
One sharing note: if your Recipes project is shared — say, with a partner — everything your assistant saves there is visible to them, which is often exactly what you want for a household cookbook. Experimenting with a surprise birthday cake? Save it to a private project and move it across after the candles.
The thirty-second habit
Generate, adjust, save, glance. Do that for the next three things you cook from a chat, and you will have the beginnings of a cookbook that lives where you cook from — your phone — written in your quantities, your timings, your swaps. Planning a whole week at once is the natural next step: plan a week of meals in ChatGPT and save it in Thoughts.
Frequently asked questions
How do I save a ChatGPT recipe into Thoughts?
Create a synced Recipes project in Thoughts, connect ChatGPT or Claude once with the Thoughts MCP server, generate the recipe in chat, then ask the assistant to save the final version as a thought in Recipes with a clear title. Confirm it in the app.
Do I need to copy and paste the recipe?
No. Once connected, the assistant saves the recipe directly as a thought when you ask. Ask for the final standalone version first — ingredients, then numbered steps — so the saved note reads like a cookbook page.
Can I save the grocery list as well as the recipe?
Yes. Ask for a separate thought containing only what you need to buy, grouped by shop section with quantities. Keeping the list separate means you can use and delete it without touching the recipe.
Can Claude find a recipe I saved from ChatGPT?
Yes. Both assistants connect to the same synced Thoughts library, so a recipe saved from one conversation can be searched, read and adapted in the other.