"Methods to Test API Endpoints" matching MCP servers:

Connects a user's own Garmin data to compatible AI clients through Garmin's official Personal API, running locally over stdio with read-only access and no Garmin username or password.

MCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.

Enables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.

Fitness AI - MCP server providing AI-powered tools and automation by MEOK AI Labs

MCP server for Cronometer nutrition tracking, enabling food diary management, nutrition data retrieval, food search, and biometric tracking via Cronometer's mobile REST API.

Provides read-only access to Oura ring biometrics via the Oura API, enabling Claude to query daily summaries, sleep, readiness, stress, workouts, baselines, and heart rate data. Designed to complement a Strava connector for joint analysis of training and recovery.

Enables an MCP client to read and write a personal Garmin Connect account: activities with per-set strength detail, daily health metrics (sleep, HRV, stress, steps, readiness), planned and completed workouts, and weigh-ins with body composition. It also logs finished strength sessions and body-composition readings as FIT files so they appear in Garmin Connect like natively recorded ones.

Exposes the Oura API v2 as an MCP server with tools to query all 19 data collections (e.g., sleep, heartrate) with automatic pagination and explicit truncation warnings.

MCP server for Cronometer nutrition tracking using the mobile API. Enables food logging, nutrition data retrieval, diary management, and fasting tracking.

Enables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.

MCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.

MCP server for the Oura Ring API v2, enabling natural language queries about sleep, readiness, activity, heart rate, and more.

Enables AI assistants to query a user's own Garmin Connect training, health, and recovery history through Garmin's official Personal API, backed by a local cache and built-in analysis tools.

A read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.

Enables AI agents to sync WHOOP recovery, sleep, workouts, cycles, and body-measurement data into a local Postgres database and query it through fast, offline-capable MCP tools without repeatedly hitting WHOOP API rate limits.

Gives Claude access to your WHOOP health data including recovery, sleep, workouts, cycles, body measurements, and profile via the WHOOP Developer API.

Unofficial MCP server for Fitatu, the Polish calorie counter: read and log food, weight, water, body measurements and workouts, check calories and macros left, set goals and get weekly reports. 47 tools (26 read-only), read-only and demo modes, stdio or HTTP with a token, free and Premium accounts.

An MCP server that exposes the Hevy fitness API as 22 tools, enabling AI agents to manage workouts, routines, exercise templates, and body measurements through natural language.

MCP server for the Oura Ring API v2, providing access to sleep, activity, readiness, heart rate, and workout data via OAuth.

This server lets Claude, Cursor, or any MCP client read a user's own health and fitness data through 26 read-only tools for activities, sleep, HRV, Body Battery, stress, steps, heart rate, weight, nutrition, and women's health. It connects via the official Personal API and can be self-hosted for free on Vercel.

An MCP server and CLI for logging food to Lose It!, enabling food search, diary management, meal logging, and weight recording via unofficial API.

Enables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.

Connects Claude to your Strava fitness data, enabling natural language queries about your training history such as activities, stats, and routes.

Enables read-only querying of your own Garmin Connect data — sleep, HRV, resting HR, Body Battery, activities, training volume, body composition, and nutrition — through Garmin's official Personal API using a revocable key. Returns compact, unit-labelled JSON shaped around questions so whole date ranges fit in context.

Enables AI assistants like Claude to read a single user's own Strava account through its API: profile and totals, activities with laps, splits, zones and per-second streams, plus segments, routes, gear and clubs. It is strictly read-only, using the user's own Strava API application and OAuth tokens stored locally, and returns model-friendly, context-sized data.

Enables users to access and query Oura ring health data, including sleep periods, readiness, activity, workouts, heart rate, stress, SpO2, resilience, and more, through Claude.ai or Claude Code using the Oura API v2 with OAuth 2.1 login.

Fetches body composition data (weight, body fat percentage) from the Tanita Health Planet API and exposes it as MCP tools for AI agents like Claude Desktop.

An MCP server that exposes Strava v3 API as read-only tools for AI agents. It covers athlete profiles, activities, stats, routes, segments, and rate limits, with OAuth2 authorization handled via a companion HTTP server.

Enables Claude to read your WHOOP health data including recovery, sleep, strain, and workouts through the official WHOOP API, so you can ask natural language questions about your fitness metrics.

MCP server for the Concept2 Logbook API, enabling user profile management, workout result operations, and challenge queries.