Documentation

athletedata for Claude

athletedata connects your training and health apps (Garmin, WHOOP, Oura, Hevy, Apple Health and 28 more) and lets Claude read them through one MCP server. Ask about your training load, sleep, HRV, power curves or race readiness, and Claude answers from your real data instead of guesses.

It comes in two forms that use the same server: the athletedata connector (the tools) and the athletedata plugin (the connector plus skills that teach Claude how to analyse training data). Both are published by HealthspanOS AG, the company behind athletedata.

What you need

  • An athletedata account with an active subscription, either the MCP plan or the Coaching plan. Both start with a 7-day free trial. See pricing.
  • At least one connected app on your integrations page. Without one, the tools have nothing to read.
  • A Claude plan that supports connectors. The connector works in claude.ai (web, desktop and mobile), Cowork and Claude Code.

Install

From the Claude directory

  1. In Claude, open Customize and search the directory for athletedata.
  2. Add the connector or the plugin, then select Connect.
  3. Claude sends you to athletedata. Sign in, check that the account shown is yours, review what Claude will be allowed to do (see permissions) and select Connect.

A plugin you add in claude.ai also appears in your Claude Code sessions.

As a custom connector

Add a custom connector with the URL https://mcp.athletedata.health/mcp. The URL is the same for everyone; signing in is what ties it to your account. The Claude setup guide walks through it with screenshots.

In Claude Code

claude mcp add --transport http athletedata https://mcp.athletedata.health/mcp

Then run /mcp in a session and sign in.

Sign-in and permissions

The connector uses OAuth 2.1 with PKCE. Claude never sees your athletedata password or the passwords and tokens of the apps you connected; it receives an access token that is only valid for this server.

The consent screen lists what the connection will be allowed to do before you approve it. There are two permission levels:

  • Read (mcp:read): Claude can read your data. Every connection has it.
  • Write (mcp:write): Claude can also take the actions listed below, such as sending a workout to your watch or logging a meal. Claude requests it by default. On a connection without it, the tools that change anything are not offered to Claude at all.

Every tool is labelled read-only or write. Claude asks for your permission before running a write tool unless you have told it to always allow that tool.

Revoking access: open Settings on athletedata and remove Claude under Connected apps. Access ends immediately, not when a token expires. You can also disconnect the connector in Claude.

What Claude can read

Data from the apps you connected, plus metrics athletedata computes from it:

  • Workouts: activities, laps, heart rate, pace, power and cadence streams, personal records, power and pace curves, planned workouts.
  • Recovery: sleep and sleep stages, HRV, resting heart rate, readiness and recovery scores, stress, respiration.
  • Body: weight, body composition, blood pressure.
  • Strength and nutrition: strength workouts and routines, food logs and macros.
  • Computed analytics: training load (CTL, ATL, TSB), intensity distribution, zones, trends, anomalies, goal reality checks.
  • Context: your calendar (if connected), weather for your location, and documents you uploaded to your health vault.

Data from Strava's API is not available through the connector, because Strava's API terms do not allow serving it to third-party AI tools. If you imported your own Strava history export into athletedata, Claude can read those imported activities.

What Claude can change

With write permission, these 26 tools can change data in athletedata or in an app you connected. Each one only runs when Claude calls it for your request, and Claude asks you first unless you allowed it.

ToolEffect
Create Coaching Note
coaching_note_create
Adds
Delete Food Log Entry
food_log_delete
Removes
Delete Workout from Watch
delete_workout_from_watch
Removes
Google Calendar: Create Event
google_calendar_create_event
Adds
Google Calendar: Delete Event
google_calendar_delete_event
Removes
Google Calendar: Update Event
google_calendar_update_event
Changes
Hevy: Create Exercise Template
hevy_create_exercise_template
Adds
Hevy: Create Routine
hevy_create_routine
Adds
Hevy: Create Routine Folder
hevy_create_routine_folder
Adds
Hevy: Create Workout
hevy_create_workout
Adds
Hevy: Update Routine
hevy_update_routine
Changes
Hevy: Update Workout
hevy_update_workout
Changes
intervals.icu: Delete Workout
intervals_delete_workout
Removes
intervals.icu: Move Workout
intervals_move_workout
Changes
intervals.icu: Upsert Workout
intervals_upsert_workout
Changes
Log Food Entry
food_log_entry
Adds
Push Workout to Watch
push_workout_to_watch
Adds
Set FTP
set_ftp
Changes
Set Units
set_units
Changes
Team: Create Coaching Note
team_note_create
Adds
Coach and clinic accounts only
TrainingPeaks: Create Workout
trainingpeaks_create_workout
Adds
TrainingPeaks: Delete Workout
trainingpeaks_delete_workout
Removes
TrainingPeaks: Edit Workout
trainingpeaks_edit_workout
Changes
TrainingPeaks: Move Workout
trainingpeaks_move_workout
Changes
Update Food Log Entry
food_log_update
Changes
Update Workout on Watch
update_workout_on_watch
Changes

Every other tool only reads.

Things to ask

  • How has my training load changed over the last 6 weeks?
  • Is my HRV trending down, and does it line up with my sleep?
  • What were my best 5-minute and 20-minute power this year?
  • Am I on track for a sub-3:30 marathon in April?
  • Build tomorrow's 5x3 min threshold session and send it to my watch.

Data handling

  • A tool returns only the data needed to answer the request it was called for. Anthropic receives that response and handles it under its own privacy policy.
  • We do not receive your Claude conversations. We log which tool was called, whether it succeeded and how large the answer was, not the question or the data returned.
  • We do not sell your data and do not use it to train AI models. How long we keep it is in section 8 of our privacy policy. You can delete your account and data from your dashboard at any time.
  • More on security and our subprocessors is in the Trust Center.

Limitations

  • Data is as fresh as the source app's last sync. Most apps deliver within minutes of a workout or a night's sleep; some sync a few times a day.
  • Tools for an app you have not connected return a message saying so, with a link to connect it.
  • Team and clinic tools are only available to coach and clinic accounts.
  • athletedata provides training information, not medical advice.

Troubleshooting

  • Claude never asked you to sign in: check the URL is exactly https://mcp.athletedata.health/mcp, with nothing after it.
  • Tools say your subscription is inactive: check your billing page.
  • Signed in as the wrong account: disconnect the connector in Claude, sign out of athletedata, and connect again.
  • Claude says it cannot see an app: check the app shows as connected on your integrations page.

Support and publisher

Email team@athletedata.health and a person on our team will answer. For privacy requests, email privacy@athletedata.health.

Published by HealthspanOS AG, Zurich, Switzerland (UID CHE-487.485.110). Terms · Privacy · Legal notice