Skip to main content
Glama

Pace

by app.run.europe-west1.pace-mcp-820971109121
OverviewDiscussions(1)Admin

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.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.1% over 38 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.2/5.0

Scored across 16 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but get_activity_data and get_workout_list both return training activities over a date range with overlapping fields, and get_recovery_status and get_daily_summary both surface HRV/RHR. Descriptions provide hierarchy hints (e.g., list vs detail), yet an agent may still hesitate between these pairs.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (get_activity_data, get_sleep_samples, etc.), with the sole exception of predict_nightly_recovery, which is still a clear verb_noun construction. No mixed conventions or stylistic deviations.

Tool Count4/5

16 tools is slightly above the ideal 3–15 range, but each tool covers a distinct data domain (activity, body, nutrition, sleep, recovery, workouts) or a necessary drill-down (samples, laps, details). No obvious filler tools, though the set is on the heavy side.

Completeness5/5

The surface comprehensively covers read-only fitness data retrieval: overview, devices, daily summaries, activities, workouts with detailed/sample/lap drill-downs, sleep with samples, nutrition, body metrics, trends, recovery status, and even a prediction tool. No significant gaps for the stated purpose.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Removeddelete_planned_workout
    • Removedget_planned_workouts
    • Removedplan_workout
    • Removedupdate_planned_workout
  2. 1 tool update
    • Addedpredict_nightly_recovery
  3. 4 tool updates
    • Addeddelete_planned_workout
    • Addedget_planned_workouts
    • Addedplan_workout
    • Addedupdate_planned_workout
  4. 9 tool updates
    • Changedget_activity_data1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_body_data1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_daily_summary1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_nutrition_data1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_recovery_status1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_sleep_data1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_training_summary1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_trends1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • Changedget_workout_list1 field changed
      • addedInput schema / properties / prefer_provider
        Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  5. 16 tool updates
    • Addedget_activity_data
    • Addedget_body_data
    • Addedget_connected_devices
    • Addedget_daily_summary
    • Addedget_data_overview
    • Addedget_nutrition_data
    • Addedget_recovery_status
    • Addedget_sleep_data
    • Addedget_sleep_samples
    • Addedget_training_summary
    • Addedget_trends
    • Addedget_workout_detail
    • Addedget_workout_laps
    • Addedget_workout_list
    • Addedget_workout_samples
    • Removedpace_status
  6. 16 tool updates
    • Removedget_activity_data
    • Removedget_body_data
    • Removedget_connected_devices
    • Removedget_daily_summary
    • Removedget_data_overview
    • Removedget_nutrition_data
    • Removedget_recovery_status
    • Removedget_sleep_data
    • Removedget_sleep_samples
    • Removedget_training_summary
    • Removedget_trends
    • Removedget_workout_detail
    • Removedget_workout_laps
    • Removedget_workout_list
    • Removedget_workout_samples
    • Addedpace_status
  7. 15 tool updates
    • First observedget_activity_data
    • First observedget_body_data
    • First observedget_connected_devices
    • First observedget_daily_summary
    • First observedget_data_overview
    • First observedget_nutrition_data
    • First observedget_recovery_status
    • First observedget_sleep_data
    • First observedget_sleep_samples
    • First observedget_training_summary
    • First observedget_trends
    • First observedget_workout_detail
    • First observedget_workout_laps
    • First observedget_workout_list
    • First observedget_workout_samples

Related MCP Connectors

Related MCP Servers

  • Whoop MCP Server

    crerocksolid
    A
    license
    Not graded
    quality
    C
    maintenance
    Connects Whoop health data to Claude via an MCP server, enabling retrieval of recovery, sleep, strain, and workout metrics through natural language tools.
    412 npm
    MIT

  • claude-garmin

    Jack-Abyss
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server that connects Garmin Connect data to Claude, enabling training analysis, recovery checks, and personalized plans based on real metrics like HRV, training load, and activities.
    18
    MIT

  • DkwtMCP

    bynoe17
    A
    license
    A
    quality
    B
    maintenance
    Local MCP server that connects Claude Desktop with Garmin and Apple Health data to read training and recovery, estimate heart rate and pace zones, analyze performance, and create structured workouts.
    22
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources