Fueling a long run with Runna, Strava and Forkmate in Claude

Short answer: eat for the training you’re actually doing, not the training you wish you’d done. For a long run, that means a carb-forward meal 1–4 hours before (1–4 g of carbohydrate per kg of body weight), about 30–60 g of carbohydrate an hour once you’re out longer than about an hour, and carbs plus 20–40 g of protein afterwards [S2, S4]. The useful part is matching those ranges to your week. With Strava’s connector and Forkmate both connected to Claude, you can ask one question and Claude reads your recent runs and what you’ve logged, then builds the plan around foods you already eat.

This post walks through two example conversations, then the ranges behind them.

What’s connected to what

• Forkmate is a free food log you fill in by telling Claude what you ate. It’s in Claude’s connector directory; connecting takes about two minutes. Through it, Claude can read a day (get_day) or a date range (get_range) of your diary, see your most-logged foods (get_usual_foods), and correct an entry (update_meal).
• Strava publishes its own official Claude connector. In Claude, it’s under Customize → Connectors; it gives Claude read-only access to your activity history and training trends, and it needs a Strava subscription (Strava’s help article).
• Runna has no Claude connector that we could find. If your Runna runs sync to Strava (Runna’s help says runs recorded in its app upload automatically once the two are connected; Runna help), Claude sees them through Strava like any other run. Tell Claude what your plan has scheduled.
• Garmin has no official Claude connector either. Community-built Garmin MCP servers exist; Forkmate’s founder wrote about setting one up in your Garmin is collecting data you’ll never read.

To be precise: Forkmate has no link to Strava, Runna or Garmin. Claude reads your training through Strava’s connector, and Forkmate only holds the food you ask Claude to log. Forkmate doesn’t count exercise calories or adjust your goal for training. Claude does the side-by-side.

Example 1: “Help me fuel a 15k tomorrow”

This is an illustrative example: a fictional runner, Sam, 60 kg, with made-up numbers. It follows the shape of a real conversation, not anyone’s real data.

Look at my Runna and Strava training, and using Forkmate, help me fuel with my favourite foods so I can run a 15k tomorrow.

Here’s what Claude did, in order:

1. Checked recent training first. Through Strava, it saw Sam hadn’t logged a run in about six months: walks, football and a few bike rides, but nothing over 5 km on foot. It said plainly that 15 km from there is a big jump: in a large study of runners, a run more than 10% longer than their longest in the previous month was linked to more overuse injuries, and runs more than double that carried the highest risk [S8]. It suggested run/walk intervals at an easy pace, offered to plan a shorter run instead, and said stopping early is part of the plan, not a failure.
2. Noted what it couldn’t see. Runna wasn’t connected, so it asked what the plan had scheduled rather than guessing.
3. Read today’s food. Through Forkmate’s get_day, it saw about 500 kcal and 25 g of carbohydrate logged so far, so the evening mattered.
4. Built the plan from Sam’s own foods. Using get_usual_foods, it picked from what Sam logs most:
   • Tonight: a carb-forward dinner, plus a snack before bed if dinner was light (rice, toast with honey, or cereal).
   • 2.5–3 hours before: about 1 g of carbohydrate per kg, so roughly 60 g for Sam: two slices of white toast with a teaspoon of honey and a medium banana, an egg if that sits well, coffee if it’s normal for Sam, and fluids [S2, S6].
   • 30–60 minutes before: a small top-up if hungry (half a banana or a gel) and some water.
   • During: a common practice is to start about 30–40 minutes in. At an easy run/walk pace, about 30 g of carbohydrate an hour to start, up to 60 g if it sits well, from gels, chews or sports drink Sam has used before [S1, S2]. Nothing new on race day.
   • After: at the next meal or snack, ideally within a couple of hours, carbs and 20–40 g of protein. For Sam, that was a favourite already in the diary: a chicken rice bowl [S4].
5. Offered to log it. When Sam confirmed breakfast, Claude logged it to Forkmate.

Example 2: “My long run is longer than anything recent”

Also illustrative: Sam again, 60 kg, generic numbers.

Using Strava, look up my last few runs. I’m doing an 18 km long run tomorrow and it’s forecast to be hot. Check what I’ve been eating in Forkmate and help me get ready.

1. Compared it to recent runs. The last run was 6 km and the longest in the past month was 14 km, so 18 km is about 30% past anything recent, a jump linked to more overuse injuries [S8]. Claude said so and offered options: an easy pace with run/walk if the heat climbs, or capping it near 15 km, about 10% past the longest recent run.
2. Estimated the cost. About 2 hours on feet, and very roughly 900–1,100 kcal: running on the flat costs about 0.8–1 kcal per kg of body weight per km, much the same at any pace, and walking breaks cost less [S7]. That figure is for sizing the fuel around the run, not a target.
3. Read the past week of food. Through get_range, it found only four days logged, and those partly. What was logged leaned on protein and fat. With that many gaps, Claude said it couldn’t tell whether Sam’s carbohydrate was actually low, so it planned carbs for the evening before and the morning rather than guessing. For reference, the position statement suggests about 3–5 g/kg a day for light training and 5–7 g/kg for around an hour a day [S2].
4. Planned for the heat. A carb-forward snack that evening, fluids with meals, and a sports drink with electrolytes during, plus moving the run earlier if possible [S3].
5. Caught a mis-logged entry. One day showed “red bell peppers, 30 oz” where Sam had meant a 30 oz sports drink. Claude pointed it out and offered to fix it; on a yes, it corrected the entry in place with update_meal, and the day’s totals changed with it.

That last step matters more than it looks. A plan built on a wrong diary is wrong too.

The ranges behind the plans

Before a long run

• 1–4 g of carbohydrate per kg, 1–4 hours before [S2]. Closer to the start, keep it smaller and lower in fat and fibre so it sits easily. For a 60 kg runner, 60 g at the low end is about two slices of white toast with a teaspoon of honey and a medium banana; the banana alone is about 27 g, and a tablespoon of honey instead of a teaspoon adds about 12 g [S6].
• Fluids: start hydrated. About 5–10 mL per kg in the 2–4 hours before (300–600 mL for a 60 kg runner) leaves time to absorb it and to pass any extra; pale-yellow urine is the sign it’s done [S2].

During

Time out	Carbohydrate	Source
Under 45 minutes	None needed	[S2]
45–75 minutes	Small amounts or a mouth rinse may help a hard effort	[S1, S2]
1–2.5 hours	About 30–60 g per hour	[S2]
Beyond about 2.5–3 hours	Up to about 90 g per hour, from glucose + fructose blends	[S1, S2]

Practise race-day fuel on training runs. The higher rates take gut training, and nothing new on the day [S1].

Fluids and heat: sweat rates vary a lot between people. The ACSM aims to keep fluid losses under 2% of body weight; weigh yourself before and after a run to find your own rate. In the heat, drinks with sodium and carbohydrate can help on longer runs [S3]. Don’t drink so much that you gain weight over a run: drinking well beyond your sweat losses can dilute blood sodium (hyponatremia), which is rarer than dehydration but more dangerous. Recreational runners are more at risk than fast ones, because they sweat less and have more time to drink. Feeling bloated, puffy, sick or confused after drinking a lot is a reason to stop drinking and get help [S2, S3].

After

• Protein: about 0.25 g per kg, or 20–40 g, per meal, spread every 3–4 hours; 1.4–2.0 g/kg across the day [S4].
• Carbohydrate: if you run again within about 8 hours, 1.0–1.2 g per kg per hour for the first 4 hours [S2]. Otherwise, normal meals usually cover it.
• Fluids: about 1.25–1.5 L for every kg of body weight lost [S2].

What more history would show

Both examples worked from thin data: a few runs, a few partly logged days. That was enough to catch a big jump and a missing evening of carbs. With weeks of consistent logging next to weeks of training, there’s more you could ask Claude to look at:

• Training load against intake. Whether your carbs rise on your big weeks or stay flat while mileage climbs.
• Long-run days next to low days. Where a heavy session sat beside a light day of eating, and how the next run felt.
• Protein spread. Whether you’re near 1.4–2.0 g/kg, in a few servings rather than one [S4].

That’s a way of using Claude with two connectors, not a Forkmate feature. Forkmate stores what you ate, with the source of every number named; Claude does the comparison when you ask. Logging most days is what makes it work, so Forkmate keeps logging to one line in chat.

Chronically under-fueling training, what the IOC calls problematic low energy availability, leads to Relative Energy Deficiency in Sport (REDs), which harms recovery, bone health and performance [S5]. If your intake next to your training looks low week after week, that’s worth raising with a doctor or a registered sports dietitian; REDs is assessed clinically, not from a food log [S5]. If the numbers ever start to feel heavy, Forkmate’s calm mode hides them everywhere while still keeping what you log.

Questions

Does Forkmate sync with Strava or Runna? No. Claude reads your training through Strava’s own connector, and Forkmate only holds your food. They never talk to each other directly.

How much do I eat before a 15k? The position statements suggest 1–4 g of carbohydrate per kg, 1–4 hours before [S2]. A comfortable starting point is the low end, about 1 g/kg, 2–3 hours out, so the meal sits easily.

Do I need to eat during a 15k? If you’ll be out over about an hour, about 30–60 g of carbohydrate an hour helps [S2]. A fast 15k under an hour may need little or nothing.

What if I haven’t trained for it? Fueling can’t stand in for training. Run/walk, slow down, or shorten the run; a run more than about 10% longer than your longest in the past month is linked to more overuse injuries [S8]. Stop for chest pain, dizziness, or pain that changes how you move. In the heat, stop, get somewhere cool and drink if you feel faint, sick, headachy or unusually tired. Confusion, a fit or collapse is an emergency: call for help [S9].

A note on safety

These ranges come from position statements written for athletes in general. They’re starting points to adjust to your gut, body and running, not prescriptions. Forkmate is a general-wellness tool, not medical advice. If you have diabetes or another medical condition, a history of disordered eating, or specific performance goals, work with a doctor or a registered sports dietitian.

The recap

1. Connect Forkmate and Strava’s connector in Claude. If your Runna runs sync to Strava, Claude sees them there.
2. Ask before the big run. Let Claude check your recent training, flag a jump, and read what you’ve eaten.
3. Before: 1–4 g/kg of carbs, 1–4 hours out [S2]. During: about 30–60 g/h past an hour [S2]. After: 20–40 g of protein [S4].
4. Fix the diary when it’s wrong. Claude can correct a mis-logged entry in place.
5. Log most days. More history gives Claude more to compare.

Open Forkmate and log your pre-run breakfast. It’s free, and you’ll make an account when you save it. Then connect it to Claude. Riding instead? Read how to fuel rides with Claude, Forkmate and Strava. Racing soon? Read how to fuel for a 10K, or how to fuel for a PR on your local route. More: calorie tracking for runners and cyclists and Forkmate for athletes.

Sources

• [S1] Jeukendrup A. A step towards personalized sports nutrition: carbohydrate intake during exercise. Sports Med. 2014;44(Suppl 1):S25–33. PubMed 24791914.
• [S2] Thomas DT, Erdman KA, Burke LM. American College of Sports Medicine Joint Position Statement: Nutrition and Athletic Performance. Med Sci Sports Exerc. 2016;48(3):543–68. PubMed 26891166. Pre-exercise 1–4 g/kg 1–4 h before; during 30–60 g/h (1–2.5 h), up to 90 g/h (over 2.5–3 h); refueling 1.0–1.2 g/kg/h for 4 h; 1.25–1.5 L per kg lost; prehydration 5–10 mL/kg 2–4 h before; daily carbs 3–5 g/kg (light) and 5–7 g/kg (moderate, about 1 h/day) (Table 2); hyponatremia risk from over-drinking.
• [S3] American College of Sports Medicine; Sawka MN et al. Exercise and fluid replacement. Med Sci Sports Exerc. 2007;39(2):377–90. PubMed 17277604. Prehydrate at least several hours before; keep losses under 2% of body weight; electrolyte and carbohydrate drinks can help over water alone; measure sweat rate by weighing before and after.
• [S4] Jäger R et al. International Society of Sports Nutrition Position Stand: protein and exercise. J Int Soc Sports Nutr. 2017;14:20. PubMed 28642676. 1.4–2.0 g/kg/day; 0.25 g/kg or 20–40 g per dose, every 3–4 h.
• [S5] Mountjoy M et al. 2023 IOC consensus statement on Relative Energy Deficiency in Sport (REDs). Br J Sports Med. 2023;57(17):1073–97. BJSM.
• [S6] USDA FoodData Central (SR Legacy): Bananas, raw, FDC 173944, 22.8 g carbohydrate per 100 g, so a medium banana (118 g) has about 27 g; Bread, white, commercially prepared, FDC 174924, 49.4 g per 100 g, so a 28 g slice has about 14 g; Honey, FDC 169640, 82.4 g per 100 g, so a tablespoon (21 g) has about 17 g and a teaspoon (7 g) about 6 g.
• [S7] Minetti AE, Moia C, Roi GS, Susta D, Ferretti G. Energy cost of walking and running at extreme uphill and downhill slopes. J Appl Physiol. 2002;93(3):1039–46. PubMed 12183501. Level running costs 3.40 J/kg/m (about 0.8 kcal/kg/km), independent of speed. The classic figure of about 1 kcal/kg/km is from Margaria R et al. Energy cost of running. J Appl Physiol. 1963;18:367–70. PubMed 13932993.
• [S8] Frandsen JSB, Hulme A, Parner ET, et al. How much running is too much? Identifying high-risk running sessions in a 5200-person cohort study. Br J Sports Med. 2025;59(17):1203–10. PubMed 40623829. Single runs more than 10% longer than the longest in the previous 30 days: overuse-injury hazard ratios 1.64 (10–30% longer), 1.52 (30–100%), 2.28 (over 100%). Observational; injuries self-reported.
• [S9] NHS. Heat exhaustion and heatstroke. nhs.uk. Roberts WO et al. ACSM Expert Consensus Statement on Exertional Heat Illness: Recognition, Management, and Return to Activity. Curr Sports Med Rep. 2021;20(9):470–84. PubMed 34524191.