Connect your AI · Runners and cyclists
Use Forkmate with Strava or Garmin
Forkmate is your food diary; Strava and Garmin hold your training. Forkmate does not connect to Strava or Garmin and never receives your activities. What works is your AI app: connect Forkmate to it, connect your training app to it separately, and ask it to read both side by side.
Below: what works today, step by step for Claude with Strava and for Garmin through Apple Health, prompts to paste, and a free Claude Skill that knows how to combine them.
What works
- Strava in Claude. Strava publishes its own read-only connector for Claude, and it needs a Strava subscription. Add it next to Forkmate in the same Claude account.
- Garmin through Apple Health. If your Garmin Connect app shares to Apple Health on your iPhone, Claude's iPhone app (US, beta, Pro and Max plans) and ChatGPT Health (US, iPhone) can read Apple Health.
- Community Garmin MCP servers. Several exist, built by individuals, not by Garmin. We have not reviewed any of them; read what one asks for before you sign in to it.
- Describing the session. Works in every app: “I ran 10K in 52 minutes this morning.”
What doesn’t
- No direct sync. Your rides and runs never reach Forkmate, and Forkmate never reaches Strava or Garmin.
- Forkmate doesn’t log workouts or count exercise calories, and it doesn’t change your calorie goal for a training day.
- Strava’s connector works in Claude, according to Strava’s help article. In ChatGPT, Gemini or Cursor, describe the session instead.
- Your AI app does the side-by-side. Its answer is general guidance, not a prescription or medical advice.
Claude with Strava, step by step
- Connect Forkmate to Claude. About a minute: Forkmate’s Claude setup. Forkmate is free; make your account first if you haven’t.
- Add Strava’s connector. In Claude, open Customize › Connectors, add Strava, and authorize it with your Strava account. Strava’s help article has the details and how to remove it later.
- Ask. Name both: “use Strava for my rides, Forkmate for my food.” Claude reads each one separately; it logs food to Forkmate only when you tell it what you ate.
Garmin, through Apple Health
- Share Garmin to Apple Health. In the Garmin Connect app on your iPhone, turn on sharing with Apple Health, and allow the workout categories in the Health permissions screen.
- Claude: in Claude’s iPhone app, connect Apple Health (US, beta, Pro and Max plans), and connect Forkmate in Claude on your phone. Then ask as you would with Strava.
- ChatGPT: Apple Health connects inside ChatGPT Health (US, iPhone). If Forkmate isn’t available in that chat, ask Health for a summary of your recent training and paste it into a chat where Forkmate is connected.
- No iPhone? Describe the session, or use a community Garmin MCP server at your own judgement.
Prompts to paste
Select one and copy it into your AI app. The Strava versions are for Claude with Strava’s connector added; the others work in any app, with the session described in words. Every one reads your food from Forkmate and nothing else.
Fuel for a PR
With Strava in Claude
Help me fuel for a PR on my local route. Use Strava to look at the route and my best efforts on it, and Forkmate to read my food diary for the last week. Ask me what you need first.
Any app, described
Help me fuel for a PR on my local route. It usually takes me about 50 minutes, with a few short climbs. Read my Forkmate diary for the last week, then give me a before, during and after plan. Ask me what you need first.
How have I been eating?
With Strava in Claude
How have I been eating, and how should I fuel for a 10K? Read the last 14 days of my Forkmate diary, and use Strava to look at my recent runs. Ask me the race date and anything else you need.
Any app, described
How have I been eating, and how should I fuel for a 10K? Read the last 14 days of my Forkmate diary. I run about four times a week and my 10K is in three weeks. Ask me anything else you need.
Fuel a long ride
With Strava in Claude
What should I eat before, during and after my long ride? Use Strava to look at my most similar recent rides, and Forkmate to read what I've eaten the last three days. Ask me what you need first.
Any app, described
What should I eat before, during and after my long ride? It's about 3 hours at a moderate pace. Read what I've eaten the last three days in Forkmate, and ask me what you need first.
Built into Forkmate’s connector
Apps that show MCP prompts list four from Forkmate: fuel-for-a-pr, fuel-for-a-race, long-ride-fueling, how-am-i-eating. Each one asks your app to read your diary, look at your training if a training app is connected there, ask what it needs, and plan before, during and after. The full text, as served:
Fuel for a PR fuel-for-a-pr
Help me fuel for a personal best on my "river loop" route, aiming for 45:00. 1. If a Strava connector is available in this chat, use it to look at my own activities and routes there. If Apple Health is connected instead (for example, my Garmin syncs to it), use that. If neither is available, ask me to describe the session: how long, how hard, and the terrain. Look at that route and my recent efforts on it: how long it usually takes me, the climbing, and how my best efforts went. 2. Read my Forkmate diary for the last 7 days (get_range), and what I ate before my best efforts there, if I logged it. 3. Before planning, ask me what you need: my body weight (for the per-kg ranges), when I plan to go, and what I usually eat beforehand and carry. Then give me a plan for the day before, before, during and after, sized to how long the effort will take. Base the plan on general sports-nutrition ranges (the ACSM, Academy of Nutrition and Dietetics and Dietitians of Canada joint position), as starting points, not a prescription: - Before: for sessions longer than about an hour, a carb-forward meal 1–4 hours out, about 1–4 g of carbohydrate per kg of body weight (the lower end the closer it is to the start), lower in fat and fibre the closer it is to the start. For shorter sessions my usual meals are usually enough. Start well hydrated. - During, by duration: under about 45 minutes, none needed; 45–75 minutes, a carb mouth rinse or small amounts, mainly when the effort is hard; 1–2.5 hours, about 30–60 g of carbohydrate per hour; beyond about 2.5–3 hours, about 60 g per hour is a sensible start, building toward up to about 90 g per hour only with glucose + fructose drinks or gels and only after practising it in training. Less is needed when the effort is easy. - Fluids: aim to keep losses under about 2% of body weight, but don't drink so much that I weigh more after than before; drinking to thirst is a sound default, and over-drinking on long events can dangerously dilute blood sodium. Weighing before and after shows my sweat rate. Drinks with sodium and carbohydrate help on long or hot sessions. - After: 20–40 g of protein. If I train again within about 8 hours, about 1.0–1.2 g of carbohydrate per kg per hour for the first 4 hours; otherwise my normal meals usually cover it. About 1.25–1.5 L of fluid for every kg of body weight lost. Keep it general: this is not medical advice. If I mention diabetes, another medical condition, pregnancy or a history of disordered eating, keep to general principles and suggest a doctor or registered sports dietitian; never work out an insulin or medication dose from my diary. If I mention missed periods, repeated injuries or stress fractures, or constant tiredness, or my complete days are often far below what my training needs, say gently that these can be signs of under-fueling (RED-S) and suggest a doctor or registered sports dietitian. Keep the tone neutral, with no praise or criticism of how much I ate and no "earned" or "burn it off" framing. If I've asked not to see numbers, describe the plan in words. Use Forkmate only for my food: read my diary there, and log food only after I confirm a meal. Keep my activity, route and training data out of Forkmate; don't pass any of it to a Forkmate tool or put it in a meal note.
Fuel for a race fuel-for-a-race
Help me fuel for a 10K on 2026-11-08. 1. Read my Forkmate diary for the last 14 days (get_range) and tell me how I've been eating: calories, carbohydrate and protein per day, and my usual meals. Treat days with little or nothing logged as missing, not as low days. 2. If a Strava connector is available in this chat, use it to look at my own activities and routes there. If Apple Health is connected instead (for example, my Garmin syncs to it), use that. If neither is available, ask me to describe the session: how long, how hard, and the terrain. Look at my recent runs to estimate how long the race will take me. 3. Before planning, ask me what you need: my body weight, the start time, my expected finish time if you can't estimate it, and foods that sit well with me. Then plan the days before, race morning, during the race and after. For the race distance: a 5K or 10K needs no carb loading, and a normal carb-forward meal beforehand is usually enough; carbs during become useful once a race runs past about 75 minutes (many half marathons). For a half marathon, a carb-forward day before is usually enough; fuller loading only helps if I'll be running for more than about 90 minutes. For a marathon, about 10–12 g of carbohydrate per kg per day for the 36–48 hours before, mostly from lower-fibre, lower-fat foods; that is a lot of food, so if I'm new to it the lower end is a reasonable start, and a temporary rise on the scale is stored carbohydrate and water, not fat. Then about 30–60 g per hour during, up to about 90 g if I have practised it. Running jostles the gut more than cycling, so anything I take during the race is something I have tried in training. Base the plan on general sports-nutrition ranges (the ACSM, Academy of Nutrition and Dietetics and Dietitians of Canada joint position), as starting points, not a prescription: - Before: for sessions longer than about an hour, a carb-forward meal 1–4 hours out, about 1–4 g of carbohydrate per kg of body weight (the lower end the closer it is to the start), lower in fat and fibre the closer it is to the start. For shorter sessions my usual meals are usually enough. Start well hydrated. - During, by duration: under about 45 minutes, none needed; 45–75 minutes, a carb mouth rinse or small amounts, mainly when the effort is hard; 1–2.5 hours, about 30–60 g of carbohydrate per hour; beyond about 2.5–3 hours, about 60 g per hour is a sensible start, building toward up to about 90 g per hour only with glucose + fructose drinks or gels and only after practising it in training. Less is needed when the effort is easy. - Fluids: aim to keep losses under about 2% of body weight, but don't drink so much that I weigh more after than before; drinking to thirst is a sound default, and over-drinking on long events can dangerously dilute blood sodium. Weighing before and after shows my sweat rate. Drinks with sodium and carbohydrate help on long or hot sessions. - After: 20–40 g of protein. If I train again within about 8 hours, about 1.0–1.2 g of carbohydrate per kg per hour for the first 4 hours; otherwise my normal meals usually cover it. About 1.25–1.5 L of fluid for every kg of body weight lost. Keep it general: this is not medical advice. If I mention diabetes, another medical condition, pregnancy or a history of disordered eating, keep to general principles and suggest a doctor or registered sports dietitian; never work out an insulin or medication dose from my diary. If I mention missed periods, repeated injuries or stress fractures, or constant tiredness, or my complete days are often far below what my training needs, say gently that these can be signs of under-fueling (RED-S) and suggest a doctor or registered sports dietitian. Keep the tone neutral, with no praise or criticism of how much I ate and no "earned" or "burn it off" framing. If I've asked not to see numbers, describe the plan in words. Use Forkmate only for my food: read my diary there, and log food only after I confirm a meal. Keep my activity, route and training data out of Forkmate; don't pass any of it to a Forkmate tool or put it in a meal note.
Fuel a long ride long-ride-fueling
What should I eat before, during and after a 3 hours ride at moderate intensity? 1. If a Strava connector is available in this chat, use it to look at my own activities and routes there. If Apple Health is connected instead (for example, my Garmin syncs to it), use that. If neither is available, ask me to describe the session: how long, how hard, and the terrain. Look at my most similar recent rides: duration, climbing and how they went. 2. Read my Forkmate diary for the last 3 days (get_range), and what I ate on my recent long ride days, if I logged it. 3. Before planning, ask me what you need: my body weight, the start time, how hard it will be if I haven't said, and what I can carry or buy on the way. Then give me a plan: the meal before, grams of carbohydrate per hour with examples (gels, drinks, bars, real food), how much to drink, and a recovery meal. When I confirm a meal I eat, offer to log it to Forkmate. Base the plan on general sports-nutrition ranges (the ACSM, Academy of Nutrition and Dietetics and Dietitians of Canada joint position), as starting points, not a prescription: - Before: for sessions longer than about an hour, a carb-forward meal 1–4 hours out, about 1–4 g of carbohydrate per kg of body weight (the lower end the closer it is to the start), lower in fat and fibre the closer it is to the start. For shorter sessions my usual meals are usually enough. Start well hydrated. - During, by duration: under about 45 minutes, none needed; 45–75 minutes, a carb mouth rinse or small amounts, mainly when the effort is hard; 1–2.5 hours, about 30–60 g of carbohydrate per hour; beyond about 2.5–3 hours, about 60 g per hour is a sensible start, building toward up to about 90 g per hour only with glucose + fructose drinks or gels and only after practising it in training. Less is needed when the effort is easy. - Fluids: aim to keep losses under about 2% of body weight, but don't drink so much that I weigh more after than before; drinking to thirst is a sound default, and over-drinking on long events can dangerously dilute blood sodium. Weighing before and after shows my sweat rate. Drinks with sodium and carbohydrate help on long or hot sessions. - After: 20–40 g of protein. If I train again within about 8 hours, about 1.0–1.2 g of carbohydrate per kg per hour for the first 4 hours; otherwise my normal meals usually cover it. About 1.25–1.5 L of fluid for every kg of body weight lost. Keep it general: this is not medical advice. If I mention diabetes, another medical condition, pregnancy or a history of disordered eating, keep to general principles and suggest a doctor or registered sports dietitian; never work out an insulin or medication dose from my diary. If I mention missed periods, repeated injuries or stress fractures, or constant tiredness, or my complete days are often far below what my training needs, say gently that these can be signs of under-fueling (RED-S) and suggest a doctor or registered sports dietitian. Keep the tone neutral, with no praise or criticism of how much I ate and no "earned" or "burn it off" framing. If I've asked not to see numbers, describe the plan in words. Use Forkmate only for my food: read my diary there, and log food only after I confirm a meal. Keep my activity, route and training data out of Forkmate; don't pass any of it to a Forkmate tool or put it in a meal note.
How have I been eating? how-am-i-eating
How have I been eating over the last 14 days, ending today? 1. Read my Forkmate diary for those 14 days (get_range). Show calories, carbohydrate and protein per day, and my averages. Treat days with little or nothing logged as missing, not as low days, and leave them out of the averages. 2. If a Strava connector is available in this chat, use it to look at my own activities and routes there. If Apple Health is connected instead (for example, my Garmin syncs to it), use that. If neither is available, ask me to describe the session: how long, how hard, and the terrain. Put my training for the same days beside the diary: what I did each day and for how long. 3. Point out training days that sat next to low-carbohydrate days, and my average protein per kg (ask my body weight, and whether I'm trying to change it, first). Daily ranges for comparison: carbohydrate about 3–5 g per kg on light days, 5–7 g per kg on moderate days (about an hour of training), 6–10 g per kg on days with 1–3 hours of moderate-to-hard training, and 8–12 g per kg on days of 4–5 hours or more; protein about 1.4–2.0 g per kg a day, spread across 3–4 meals. These assume I'm eating to hold my weight. If I'm trying to lose weight, don't treat every day as low: check that my longer or harder sessions were fuelled and that protein sits toward the top of its range. Then ask what I'm training for next, and suggest how I could fuel the coming week. Keep it general: this is not medical advice. If I mention diabetes, another medical condition, pregnancy or a history of disordered eating, keep to general principles and suggest a doctor or registered sports dietitian; never work out an insulin or medication dose from my diary. If I mention missed periods, repeated injuries or stress fractures, or constant tiredness, or my complete days are often far below what my training needs, say gently that these can be signs of under-fueling (RED-S) and suggest a doctor or registered sports dietitian. Keep the tone neutral, with no praise or criticism of how much I ate and no "earned" or "burn it off" framing. If I've asked not to see numbers, describe the plan in words. Use Forkmate only for my food: read my diary there, and log food only after I confirm a meal. Keep my activity, route and training data out of Forkmate; don't pass any of it to a Forkmate tool or put it in a meal note.
The Forkmate fueling coach, a Claude Skill
A skill is a set of instructions Claude loads when your question matches it. This one tells Claude how to combine Forkmate with Strava’s connector or Apple Health for the questions above, with general fueling ranges and the same rule: your training data stays out of Forkmate.
Download forkmate-fueling-coach.zip (one file, SKILL.md)
- In Claude, open Customize › Skills and upload the ZIP as a new skill.
- Turn the skill on. If Skills isn’t in your menu, check that code execution is on in Claude’s settings.
- Ask a fueling question; Claude loads the skill when it fits.
- Claude Code: unzip it into
~/.claude/skills/.
Read SKILL.md before you install it
--- name: forkmate-fueling-coach description: Plans what to eat before, during and after a run or ride, and reviews recent eating against training, by reading the user's Forkmate food diary and their own activities from Strava's connector or Apple Health in this app. Use when the user asks how to fuel for a PR on a route, a race (5K, 10K, half marathon, marathon) or a long ride, or how they have been eating for their training. --- # Forkmate fueling coach This skill combines two things the user has connected in this app: - **Forkmate** (the food diary): what they ate, with calories, carbohydrate, protein and fat per day. - **Their activities**, from one of: - **Strava's own connector** for Claude (a Strava subscription is needed for it). It is read-only. - **Apple Health**, if the user has connected it in the Claude app on iPhone. A Garmin watch can reach Apple Health when the user turns that on in the Garmin Connect app. - A Garmin MCP server the user added themselves. Several community-built ones exist. Garmin does not publish them, and Forkmate has not reviewed any of them. - The user's own words, if none of these is connected: how long, how hard, the terrain, how it went. Forkmate and the activity source never talk to each other. You read each one separately and put them side by side in the conversation. ## Boundaries 1. **Activity data stays out of Forkmate.** Never pass activity, route, heart-rate, power or training data to a Forkmate tool, and never put it in a meal's note or name. Forkmate has no exercise tool; do not try to log a workout there. 2. **Read food with `get_range`** (start and end dates, YYYY-MM-DD, at most 93 days) or `get_day` for one day. Use `get_preferences` before suggesting foods, so allergies and dislikes are respected. 3. **Log food only after the user confirms a meal they ate**, with `log_meal`, in their own words. A plan is not a meal; never log planned food in advance. 4. **Never describe Forkmate as linked to Strava or Garmin.** There is no link between them. 5. If no activity source is connected, say so plainly and ask the user to describe the session instead. ## Workflows ### "Help me fuel for a PR on my local route" 1. Activity source: find the route or segment and the user's recent efforts on it (duration, climbing, best efforts). 2. Forkmate: `get_range` for the last 7 days; note what they ate before their best efforts there, if logged. 3. Ask: body weight (for per-kg ranges), when they plan to go, what they usually eat beforehand and carry. 4. Plan: the day before, the pre-session meal, during (by expected duration), after. ### "How have I been eating and how should I fuel for a 10K?" 1. Forkmate: `get_range` for the last 14 days. Show calories, carbohydrate and protein per day and the averages. Treat days with little or nothing logged as missing, not low, and leave them out of averages. 2. Activity source: recent runs, to estimate the finish time. 3. Ask: body weight, race date and start time, foods that sit well. 4. Plan: the days before, race morning, during, after. Apply the race notes below. ### "What should I eat before, during and after my long ride?" 1. Activity source: the most similar recent rides (duration, climbing, how they went). 2. Forkmate: `get_range` for the last 3 days, and what they ate on recent long-ride days if logged. 3. Ask: body weight, start time, intensity, what they can carry or buy on the way. 4. Plan: the meal before; grams of carbohydrate per hour with example foods (gels, drinks, bars, real food); fluids; a recovery meal. Offer to log a meal once they confirm they ate it. ### "How am I eating for my training?" (a review) 1. Forkmate: `get_range` for the period (14 days unless the user says otherwise). 2. Activity source: training each day for the same dates. 3. Point out training days next to low-carbohydrate days, and average protein per kg (ask body weight, and whether they are trying to change it, first). Compare with the daily ranges below. 4. Ask what they are training for next, and suggest how to fuel the coming week. ## Fueling ranges General ranges from the ACSM / Academy of Nutrition and Dietetics / Dietitians of Canada joint position (2016), Jeukendrup (2014), the ACSM fluid position stand (2007) and the ISSN protein position stand (2017). They are starting points, not a prescription. | When | Range | |---|---| | Before | For sessions longer than about an hour: a carb-forward meal 1–4 hours out, about 1–4 g of carbohydrate per kg of body weight (the lower end the closer it is to the start), lower in fat and fibre the closer it is to the start. For shorter sessions, usual meals are usually enough. Start well hydrated. | | During, under about 45 min | None needed. | | During, 45–75 min | A carbohydrate mouth rinse or small amounts, mainly when the effort is hard. | | During, 1–2.5 h | About 30–60 g of carbohydrate per hour. | | During, beyond about 2.5–3 h | About 60 g per hour is a sensible start, building toward up to about 90 g per hour only with glucose + fructose drinks or gels and only after practising it in training. Less when the effort is easy. | | Fluids | Keep losses under about 2% of body weight, but not so much drinking that the user weighs more after than before; drinking to thirst is a sound default, and over-drinking on long events can dangerously dilute blood sodium. Weighing before and after shows the sweat rate. Drinks with sodium and carbohydrate help on long or hot sessions. | | After | 20–40 g of protein. Training again within about 8 hours: about 1.0–1.2 g of carbohydrate per kg per hour for the first 4 hours; otherwise normal meals usually cover it. About 1.25–1.5 L of fluid per kg of body weight lost. | **Race notes.** A 5K or 10K needs no carb loading; a normal carb-forward meal beforehand is usually enough. Carbohydrate during becomes useful once a race runs past about 75 minutes. For a half marathon, a carb-forward day before is usually enough; fuller loading only helps beyond about 90 minutes of running. For a marathon: about 10–12 g of carbohydrate per kg per day for the 36–48 hours before, mostly from lower-fibre, lower-fat foods; that is a lot of food, so the lower end is a reasonable start for a first-timer, and a temporary rise on the scale is stored carbohydrate and water, not fat. Then about 30–60 g per hour during, up to about 90 g if practised. Running jostles the gut more than cycling, so race-day food is food already tried in training. **Daily ranges for a review.** Carbohydrate about 3–5 g/kg on light days, 5–7 g/kg on moderate days (about an hour of training), 6–10 g/kg on days with 1–3 hours of moderate-to-hard training, and 8–12 g/kg on days of 4–5 hours or more. Protein about 1.4–2.0 g/kg a day, spread across 3–4 meals. These assume the user is eating to hold their weight. If they are trying to lose weight, do not treat every day as low: check that longer or harder sessions were fuelled and that protein sits toward the top of its range. Ask about body weight, and whether they are trying to change it, before giving per-kg figures. ## Output - Lead with a short plan: before, during (grams of carbohydrate per hour and example foods), fluids, after. - Show the per-kg arithmetic once, so the user can check it. - Forkmate's calorie and macro values are estimates; say so when a number matters. - If the user has asked not to see numbers, give the plan in words only. ## Care - This is general sports-nutrition guidance, not medical advice. - If the user mentions diabetes, another medical condition, pregnancy or a history of disordered eating, keep to general principles and suggest a doctor or registered sports dietitian. Never compute an insulin or medication dose from diary numbers. - If the user mentions missed periods, repeated injuries or stress fractures, or constant tiredness, or their complete days are often far below what their training needs, say gently that these can be signs of under-fueling (RED-S) and suggest a doctor or registered sports dietitian. - Keep the tone neutral: no praise or criticism of how much someone ate, and no "earned" or "burn it off" framing. Under-fueling, not over-eating, is the usual risk in endurance training.
ChatGPT, Gemini and Cursor
Connect Forkmate (ChatGPT, Gemini, Cursor), then paste one of the “any app” prompts above and describe the session. Each setup page has the same starters.
Further reading
- How to fuel for a PR on your local route, with Claude, Strava and Forkmate
- How to fuel for a 10K: look back at how you’ve been eating first
- What to eat before, during and after a long ride
- How I stopped bonking: fueling rides with Claude, Forkmate and Strava
- Fueling a long run with Runna, Strava and Forkmate in Claude
- Forkmate for runners and cyclists
The ranges in these prompts are general starting points from sports-nutrition position statements, not medical advice. If you have diabetes or another medical condition, are pregnant, or have a history of disordered eating, work with a doctor or a registered sports dietitian.
Checked against Strava: What is the Strava MCP connector?, Claude Help Center: Use Claude with iOS apps, OpenAI Help Center: Using ChatGPT Health, Claude docs: Create custom skills. Strava, Garmin, Apple Health and the AI apps change their menus and plans; trust what yours shows.
Start your food diary
Forkmate is free. Connect it to the AI app you already use, then ask it about your training.