Server Details
Pace is a remote MCP server that exposes wearable and fitness data to Claude via the Model Context Protocol. It connects to Garmin, Oura, Whoop, Polar, Fitbit and 20+ devices and provides 15 tools for querying sleep, activity, recovery, and training data. Hosted on Google Cloud Run, OAuth 2.1 authentication, Streamable HTTP transport. Instructions: First you need to create an account at: https://pacetraining.co and connect your wearables. After that you can connect the remote Server via Custom Connector in Claude and OAuth 2.1 Flow startet.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
15 toolsget_activity_dataInspect
Retrieves training activities for the user over a specified date range. Shows distance, duration, pace, heart rate, calories, and training load.
Parameters:
start_date: Start date in YYYY-MM-DD format
end_date: End date in YYYY-MM-DD format
activity_type: Optional. Filter: 'RUNNING', 'CYCLING', 'STRENGTH_TRAINING', etc.
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | ||
| start_date | Yes | ||
| activity_type | No |
get_body_dataInspect
Retrieves body measurement data: weight, body fat, muscle mass, and BMI.
Parameters:
start_date: Start date in YYYY-MM-DD format
end_date: End date in YYYY-MM-DD format
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | ||
| start_date | Yes |
get_connected_devicesInspect
Lists all connected wearables and fitness trackers. Shows status, last sync time, and Terra User ID.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_daily_summaryInspect
Shows the daily summary for a specific date: steps, active time, calories, resting heart rate, HRV, and stress level.
Parameters:
date: Date in YYYY-MM-DD format
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes |
get_data_overviewInspect
Shows an overview of all available fitness data for the user. Lists connected devices and available data date ranges. Claude should call this tool first to understand what data is available.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_nutrition_dataInspect
Retrieves nutrition data: calories, macronutrients (protein, carbs, fat), and water intake.
Parameters:
start_date: Start date in YYYY-MM-DD format
end_date: End date in YYYY-MM-DD format
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | ||
| start_date | Yes |
get_recovery_statusInspect
Shows current recovery status: device scores (Recovery, Readiness, Strain), HRV and resting heart rate trend over the last 7 days with 28-day baseline, sleep quality of the last 3 nights, and training load. All values come directly from the wearable — no custom calculations except average/min/max.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_sleep_dataInspect
Retrieves sleep data for the user over a specified date range. Shows sleep duration, sleep stages (deep, REM, light), HRV, SpO2, breathing rate, and sleep score.
Parameters:
start_date: Start date in YYYY-MM-DD format
end_date: End date in YYYY-MM-DD format
source: Optional. Provider filter e.g. 'GARMIN' or 'OURA'
| Name | Required | Description | Default |
|---|---|---|---|
| source | No | ||
| end_date | Yes | ||
| start_date | Yes |
get_sleep_samplesInspect
Retrieves time-series data for a sleep night: HR progression, HRV, SpO2, breathing rate, or hypnogram (sleep stage progression). Requires sleep_id from get_sleep_data and sample_type ('hr', 'hrv', 'spo2', 'breathing', 'hypnogram').
Parameters:
sleep_id: UUID of the sleep night from get_sleep_data
sample_type: 'hr', 'hrv', 'spo2', 'breathing', or 'hypnogram'
| Name | Required | Description | Default |
|---|---|---|---|
| sleep_id | Yes | ||
| sample_type | Yes |
get_training_summaryInspect
Aggregated training statistics over a time period: number of workouts, total duration and distance per sport, weekly overview, intensity distribution, and training load. Ideal for training reports, progress analysis, and periodization overview.
Parameters:
period: '7d', '30d', '90d', '180d', or '365d'
activity_type: Optional. Filter by sport: 'RUNNING', 'CYCLING', etc.
| Name | Required | Description | Default |
|---|---|---|---|
| period | Yes | ||
| activity_type | No |
get_trendsInspect
Shows trends and developments for a specific health metric over time. Compares the current period with the previous (equally long) period.
Parameters:
metric: One of: 'hrv', 'sleep_duration', 'sleep_score', 'sleep_efficiency', 'readiness', 'resting_hr', 'steps', 'active_minutes', 'weight', 'body_fat', 'stress', 'strain', 'vo2max', 'training_load'
period: Time period: '7d', '30d', or '90d' (default: '30d')
| Name | Required | Description | Default |
|---|---|---|---|
| metric | Yes | ||
| period | No | 30d |
get_workout_detailInspect
Shows all details of a single workout: heart rate, pace, cadence, power, intensity zones, elevation, calories, and more. Requires workout_id from get_workout_list. Also shows which sample data (HR time series, speed, GPS etc.) is available — these can be retrieved with get_workout_samples.
Parameters:
workout_id: UUID of the workout from get_workout_list
| Name | Required | Description | Default |
|---|---|---|---|
| workout_id | Yes |
get_workout_lapsInspect
Shows lap/split data for a workout: distance, time, pace, heart rate per lap. Requires workout_id from get_workout_list. Ideal for run analysis, interval evaluation, and pacing strategy.
Parameters:
workout_id: UUID of the workout from get_workout_list
| Name | Required | Description | Default |
|---|---|---|---|
| workout_id | Yes |
get_workout_listInspect
Lists all workouts in a date range — compact overview with type, duration, distance, pace, and heart rate. Use this tool first for an overview. For details on a single workout, use get_workout_detail. The workout ID in the output can be used with get_workout_detail and get_workout_samples.
Parameters:
start_date: Start date in YYYY-MM-DD format
end_date: End date in YYYY-MM-DD format
activity_type: Optional. Filter: 'RUNNING', 'CYCLING', 'STRENGTH_TRAINING', etc.
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | Yes | ||
| start_date | Yes | ||
| activity_type | No |
get_workout_samplesInspect
Retrieves detailed time-series data for a workout: HR progression, speed, power, cadence, elevation profile, or GPS route. Requires workout_id from get_workout_list and sample_type ('hr', 'speed', 'power', 'cadence', 'elevation', 'gps'). Data is presented as 1-minute averages. Ideal for progression analysis and pattern detection.
Parameters:
workout_id: UUID of the workout from get_workout_list
sample_type: 'hr', 'speed', 'power', 'cadence', 'elevation', or 'gps'
| Name | Required | Description | Default |
|---|---|---|---|
| workout_id | Yes | ||
| sample_type | Yes |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
Hi Anton here, I am a former professional Athlete and build this mainly for myself. I would appreciate your thoughts about this project. I personally use it everyday, especially the new "visualization" tool in Claude makes this 10x more powerful.