PaceBeats

Bring your training plan, recent sessions, and race goals into your AI.

Connect your AI to your PaceBeats training account to review today’s workout, understand your weekly plan, summarize recent training, and prepare for upcoming races. Read stored coaching rationale, strength sessions, race results, and changes to your plan.

What you can ask

What training do I have planned today?
Example path

MCP connector

Server URL: https://mcp.pacebeats.com/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: PaceBeats holds the connected athlete's plan and training record. Reads are always available; writes are optional permissions, off by default and unavailable under 18. Route by question: (today or a day within 7 days, with block structure and zones), (any week from 8 back to 12 ahead), (one session; needs a session_ref from another tool), (coming weeks and phases), (totals and trends), (race calendar; a race_ref gives one race's verdict, prediction, pacing, taper), (confirmed result, splits, debrief), (how a past week went), (why the plan changed, suggestions waiting), (gym lifts and logged sets), (assumptions, availability, connections, generation state), (fitness, fatigue and form labels; metrics.read), (whether to go ahead with a session; wellness.read and/or metrics.read), (zone ranges, threshold freshness; metrics.read), (product help). A field that comes back not_available names the missing optional permission: tell the athlete to reconnect and allow it rather than guessing. Four write tools need plan.log or plan.propose: records how a planned session went, records one gym set, stages ONE change (move, shorten, lengthen, skip, swap_easy or a lighter week), notes illness, injury, travel or fatigue. , , and use preview then commit: the first call leaves the workout, set, or disruption note unchanged and returns a preview and a short-lived confirmation_token; show the preview, including any saved values it will replace, get the athlete's agreement, then call again with the same fields plus the token. Calls may still record audit events. saves a pending proposal on its first call and does not accept a confirmation_token; show its summary, expiry and confirm_options.in_app_url so the athlete can review and approve it in PaceBeats. Never invent a token or a ref. Plan changes are only ever confirmed by the athlete in the PaceBeats app, so never say a change is made. Nothing here regenerates weeks, starts or ends constraint mode, edits races, or deletes anything. Relay returned facts; never invent training, readiness, fitness, thresholds or medical advice; raw load, HRV, sleep, weight and exact threshold values are never available.

Tools

Reads data21

Changes data2

Deletes or can't be undone2

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.pacebeats.com/mcp

OAuth

Protocol

MCP 2026-07-28

Instructions

PaceBeats holds the connected athlete's plan and training record. Reads are always available; writes are optional permissions, off by default and unavailable under 18. Route by question: (today or a day within 7 days, with block structure and zones), (any week from 8 back to 12 ahead), (one session; needs a session_ref from another tool), (coming weeks and phases), (totals and trends), (race calendar; a race_ref gives one race's verdict, prediction, pacing, taper), (confirmed result, splits, debrief), (how a past week went), (why the plan changed, suggestions waiting), (gym lifts and logged sets), (assumptions, availability, connections, generation state), (fitness, fatigue and form labels; metrics.read), (whether to go ahead with a session; wellness.read and/or metrics.read), (zone ranges, threshold freshness; metrics.read), (product help). A field that comes back not_available names the missing optional permission: tell the athlete to reconnect and allow it rather than guessing. Four write tools need plan.log or plan.propose: records how a planned session went, records one gym set, stages ONE change (move, shorten, lengthen, skip, swap_easy or a lighter week), notes illness, injury, travel or fatigue. , , and use preview then commit: the first call leaves the workout, set, or disruption note unchanged and returns a preview and a short-lived confirmation_token; show the preview, including any saved values it will replace, get the athlete's agreement, then call again with the same fields plus the token. Calls may still record audit events. saves a pending proposal on its first call and does not accept a confirmation_token; show its summary, expiry and confirm_options.in_app_url so the athlete can review and approve it in PaceBeats. Never invent a token or a ref. Plan changes are only ever confirmed by the athlete in the PaceBeats app, so never say a change is made. Nothing here regenerates weeks, starts or ends constraint mode, edits races, or deletes anything. Relay returned facts; never invent training, readiness, fitness, thresholds or medical advice; raw load, HRV, sleep, weight and exact threshold values are never available.

Tools