How to use Claude as a running coach, and send its plan to Garmin
Claude writes a solid training plan when you give it a real brief: your current weekly running, a recent race time, the race date and the days you can run. It can't see your runs or reach your watch on its own. Paste its plan into PaceRunner, or add PaceRunner to Claude as a connector, and every session goes onto your Garmin calendar at your paces, with Garmin's copy checked.
What Claude is good at
Claude is careful with long, structured text, which suits a training plan: it keeps weeks in order, explains the purpose of each session when asked, and takes constraints well ("never two hard days in a row, long run on Saturday, I can't run Wednesdays"). It's also good at reading a plan you already have and saying what it's doing, or rewriting it around a holiday.
Start with a brief, in one message
Most weak AI plans come from a thin first message. Give Claude the facts up front:
| Tell it | Why | Example |
|---|---|---|
| Weekly running now | Week 1 should start near it, not at a template's number | "About 25 km (16 mi) a week over 3 runs" |
| Longest recent run | The long run builds from here | "Longest run lately: 10 km (6 mi)" |
| A recent race time | Sets the paces; without it, paces are guesses | "5K in 27:30, six weeks ago" |
| Race and date | Fixes the plan's length and taper | "10K on 22 February" |
| Days and long-run day | So sessions land on days you can run | "4 days: Tue, Thu, Sat, Sun; long run Sunday" |
| The format you want | So it can be imported | "One line per session, starting with its day" |
Prompts that work
- "Write a 10-week 10K plan ending 22 February, from where I am now (25 km a week, longest run 10 km, 5K 27:30). Four days: Tue, Thu, Sat, Sun, long run Sunday. Use effort names (easy, threshold, 10K pace, 5K pace), not paces. One line per session, starting with its day."
- "Check it: is any week more than about 15% bigger than the biggest of the three before it? Are there two hard days back to back anywhere? Fix them."
- "I missed week 4's Thursday and Sunday because of a cold. Rewrite weeks 5 to 10 so I'm not trying to make them up."
- "Give me the whole current plan again in one block."
The last prompt matters. Over a long conversation, Claude may describe a change in one message without restating the whole plan, so the full current version only exists in pieces. Asking for it whole, at the end, gives you one thing to copy. (PaceRunner's Import also reads a whole chat and keeps the last version of the plan, but a clean final copy is easier to check.)
TypeTue: 10 min easy, 5 x 1 km at 10K pace with 2 min jog, 10 min easy
Claude's blind spots
- It can't see your training. It doesn't know you skipped a run or that last week felt hard unless you say so.
- Its paces are arithmetic from what you typed. If it gives numbers, check them against a pace calculator. Better: ask for efforts and let your paces fill them in.
- It can't put anything on your watch without a connected tool.
- It follows your lead. Ask for a 50% jump in mileage and it may write one with a caveat. Audit the plan yourself: is my training plan safe.
Way 1: paste Claude's plan into PaceRunner
- Copy the plan (or the whole chat) from Claude.
- In PaceRunner, open Plans → Import, paste it, and give the race date or the day week 1 starts if the plan doesn't say.
- PaceRunner places each session on its day and builds it as Garmin steps at your paces, from a recent race time through the Daniels–Gilbert equations. Anything unclear (a recovery with no length, a "steady" that could mean two things) is asked about on its step.
- Press Send all. Each workout goes to Garmin through the official Training API, then PaceRunner reads Garmin's copy back and checks every step and target.
Way 2: add PaceRunner to Claude as a connector
PaceRunner is a remote MCP server at `https://pacerunner.app/api/mcp`. Add it in Claude as a custom connector, sign in to PaceRunner and allow it. Claude then has five tools:
| Tool | What Claude can do with it |
|---|---|
| get_profile | Read your paces by effort, units, time zone and today's date, so it writes at your real paces |
| get_calendar | See what's already planned and on Garmin, including sessions moved after a missed run |
| import_plan | Import the plan it just wrote, with a start or race date |
| send_and_check | Send the plan, or chosen sessions, to Garmin; each one is read back and checked |
| move_session | Move a session to another day; you get a warning if that breaks a safety limit |
| remove_sessions | Take sessions off your calendar, or only off Garmin, when your week changes |
| get_strength | See the strength training in your plans, with each session's exercises, sets, reps and weights |
| set_strength | Add strength training to a plan, change how often or with what, or take it out |
| update_strength_session | Move a strength session to a day you choose, or send it to your watch |
| set_strength_weight | Set the weight you lift for an exercise |
So "move Thursday's intervals to Friday, I'm working late" becomes a change on your Garmin calendar, made from the chat. The connector is for PaceRunner subscribers, and it never gives Claude your runs or health data. Setup steps: connect PaceRunner to Claude.
Questions
- Can Claude send workouts to Garmin?
- Only through a connected app. With PaceRunner added as a connector, Claude can import a plan and send it to Garmin Connect, and every workout is read back and checked.
- Can Claude see my Garmin data through PaceRunner?
- No. The connector reads your paces and your PaceRunner calendar, never runs or health data.
- Should Claude give paces or effort names?
- Effort names (easy, threshold, 10K pace, 5K pace). PaceRunner fills them in from your race time, and they update when your fitness does. Paces Claude writes out are kept as written.
- Does it work with a plan Claude wrote earlier?
- Yes. Paste the plan or the whole conversation into Import; it takes the last version of the plan.
Checked November 20, 2026