63 tools for Apple Health, Fitbit, Oura & Health Connect data in Claude, ChatGPT, Grok & Mistral.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
log_body_metrics4 fields changedInput schema / properties / bone_mass_lb / descriptionPrevious value: -"Bone mass in pounds. Optional."New value: +"Bone mass in POUNDS, always. Convert from kg if needed (kg × 2.2046). Optional."Input schema / properties / fat_mass_lb / descriptionPrevious value: -"Fat mass in pounds. Optional — calculate from weight and body fat % if not explicitly stated."New value: +"Fat mass in POUNDS, always. Convert from kg if needed (kg × 2.2046). Optional — calculate from weight and body fat % if not explicitly stated."Input schema / properties / lean_mass_lb / descriptionPrevious value: -"Lean (non-fat) mass in pounds. Optional — calculate from weight and body fat % if not explicitly stated."New value: +"Lean (non-fat) mass in POUNDS, always. Convert from kg if needed (kg × 2.2046). Optional — calculate from weight and body fat % if not explicitly stated."Input schema / properties / weight_lb / descriptionPrevious value: -"Body weight in pounds. Optional."New value: +"Body weight in POUNDS, always — regardless of the user’s display unit. If the user gave kg, convert to pounds before calling (kg × 2.2046). Optional."log_run1 field changedInput schema / properties / distance_mi / descriptionPrevious value: -"Distance in miles. Required."New value: +"Distance in MILES, always — regardless of the user’s display unit. Convert from km if needed (km ÷ 1.609344). Required."log_workout2 fields changedInput schema / properties / exercises / items / properties / sets / items / properties / band_label_lb / descriptionPrevious value: -"Band label weight in pounds (e.g. 80 for an 80lb band). Use when is_band is true. If omitted, weight_lb is used as the band label."New value: +"Band label weight in POUNDS, always (e.g. 80 for an 80lb band). Use when is_band is true. If omitted, weight_lb is used as the band label."Input schema / properties / exercises / items / properties / sets / items / properties / weight_lb / descriptionPrevious value: -"Load in pounds. For band exercises, this is the band label weight (e.g. 80 for an 80lb band). Optional — omit for bodyweight exercises."New value: +"Load in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). For band exercises, this is the band label weight (e.g. 80 for an 80lb band). Optional — omit for bodyweight exercises."update_workout4 fields changedInput schema / properties / add_exercises / items / properties / sets / items / properties / band_label_lb / descriptionPrevious value: -"Band label weight in pounds. Optional."New value: +"Band label weight in POUNDS, always. Optional."Input schema / properties / add_exercises / items / properties / sets / items / properties / weight_lb / descriptionPrevious value: -"Load in pounds. Optional."New value: +"Load in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."Input schema / properties / set_updates / items / properties / band_label_lb / descriptionPrevious value: -"Band label weight in pounds. Defaults to weight_lb if omitted. Optional."New value: +"Band label weight in POUNDS, always. Defaults to weight_lb if omitted. Optional."Input schema / properties / set_updates / items / properties / weight_lb / descriptionPrevious value: -"Corrected weight in pounds. Optional."New value: +"Corrected weight in POUNDS, always — regardless of the user’s display unit. Convert from kg if needed (kg × 2.2046). Optional."log_workout4 fields changedInput schema / properties / exercises / items / properties / sets / items / properties / rpe / descriptionPrevious value: -"Per-set Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."Input schema / properties / exercises / items / properties / sets / items / properties / rpe / typePrevious value: -"integer"New value: +"number"Input schema / properties / rpe / descriptionPrevious value: -"Session-level Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."New value: +"Session-level Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."Input schema / properties / rpe / typePrevious value: -"integer"New value: +"number"update_workout6 fields changedInput schema / properties / add_exercises / items / properties / sets / items / properties / rpe / descriptionPrevious value: -"Per-set Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."Input schema / properties / add_exercises / items / properties / sets / items / properties / rpe / typePrevious value: -"integer"New value: +"number"Input schema / properties / rpe / descriptionPrevious value: -"Session-level Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."New value: +"Session-level Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — infer from user comments about overall difficulty, or omit."Input schema / properties / rpe / typePrevious value: -"integer"New value: +"number"Input schema / properties / set_updates / items / properties / rpe / descriptionPrevious value: -"Per-set Rate of Perceived Exertion (1-10, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."New value: +"Per-set Rate of Perceived Exertion (1-10, half steps like 7.5 allowed, where 5=moderate, 7=hard, 9=one rep left, 10=failure). Optional — include only if the user specifies effort for individual sets."Input schema / properties / set_updates / items / properties / rpe / typePrevious value: -"integer"New value: +"number"cancel_rest_daydelete_cycledelete_injurydelete_mealdelete_recovery_sessiondelete_rundelete_wellbeingdelete_workoutget_app_guide_sectionget_exercise_historyget_workoutlist_blog_postslist_body_metricslist_cyclelist_exerciseslist_injurieslist_lab_markerslist_lab_resultslist_mealslist_recovery_strategieslist_rest_dayslist_runslist_sleeplist_supplementslist_wearable_datalist_wellbeinglist_workoutslog_body_metricslog_cyclelog_injurylog_lab_resultslog_meallog_recovery_sessionlog_rest_daylog_runlog_sleeplog_supplement_takenlog_wearablelog_wellbeinglog_workoutmanage_recovery_strategymanage_supplementshow_body_weightshow_exercise_progressionshow_fit_score_breakdownshow_recoveryshow_runsshow_week_fit_scoreshow_week_macrosshow_week_sleepshow_week_stepsshow_week_workoutsshow_workoutupdate_cycleupdate_injuryupdate_mealupdate_recovery_sessionupdate_wellbeingupdate_workoutClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
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.
No comments yet. Be the first to start the discussion!
Garmin data in Claude: 135 tools — activities, sleep, HRV, training, workouts. Free, open source.
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
Private Apple Health metrics and workout detail for ChatGPT, Claude, and any MCP client.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Add one secure layer between your agents and this server.
Each tool targets a distinct domain and action, and descriptions are detailed enough to separate similar tools (e.g., show_week_workouts vs get_workout). However, the sheer number of list_*/log_*/delete_* tools plus combined manage_* tools could occasionally cause misselection, especially between manage_recovery_strategy and log_recovery_session.
The set follows a consistent verb_noun snake_case pattern throughout, with predictable families: list_*, log_*, update_*, delete_*, get_*, show_*, and manage_*. The show_week_* and show_* prefixes clearly indicate visualization tools.
59 tools is far beyond the typical well-scoped range (3-15). While the fitness domain is broad, the surface could be consolidated (e.g., combined CRUD managers like manage_supplement; many delete_* could fold into update or manage operations). The large selection space increases agent confusion and latency.
The surface covers CRUD/lifecycle for nearly every domain (workouts, meals, sleep, cycle, injuries, labs, supplements, recovery, wellbeing, wearables, runs, body metrics), with upserts covering update for several, and rich analytics via show_* tools. Minor gap: no update_run, so correcting a run requires delete and re-log; some domains lack explicit delete (wearables, sleep, body metrics) but rely on upserts instead.
