"Connecting to an External API for Agent-Based Replies" matching MCP servers:

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

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

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

A universal fitness intelligence layer for AI assistants like Claude, ChatGPT, and Copilot, enabling user profiles, workout/diet plans, calendar scheduling, and gamification via MCP and REST APIs.

Your AI running coach that actually remembers. An MCP server with persistent memory that connects your Strava data to Claude — tracking your zones, pace trends, injuries, and goals across sessions so coaching advice stays current.

Enables Claude to act as a personal health coach by connecting to Garmin wearable data and Notion workspace for automated calorie tracking, photo food logging, and coaching insights.

Connects WHOOP fitness data to Poke AI assistant, enabling natural language queries for recovery scores, sleep analysis, strain tracking, and healthspan metrics.

An MCP server that provides an interface to Google's Fitness API, enabling interaction with fitness data through natural language using the Multi-Agent Conversation Protocol.

Exposes over 90 Garmin Connect tools for tracking activities, health metrics, and training data through the Model Context Protocol. It is optimized for Poke compatibility and supports deployment to Render via HTTP.

Enables AI agents like Claude Desktop, Cursor, and VS Code to connect directly to COLMI R02/R03 and compatible smart rings over local Bluetooth LE, exposing tools for ring scanning, battery and firmware status, activity and sleep/recovery insights, real-time heart rate and SpO2 vitals, 3-axis motion sampling, clock sync, and physical LED blinking. Runs fully locally with no vendor cloud, accounts, or subscriptions.

Read-only MCP server exposing daily health facts, 7/28-day baselines, and deterministic daily pulse from Google Health API data.

Enables users to search and retrieve fitness exercise information from the Api Ninjas database. It supports filtering by exercise name, target muscle, type, and difficulty level.

HYBRD manage your wearables connection, is a system of record for your training plan / completed workouts, and steers LLMs towards giving better fitness coaching

A health-data MCP server with per-user authorization using JWT tokens, enabling secure access to fitness data like profiles, progress, meal logs, workout logs, and weight logs through MCP tools.

Enables the agent to record meals, workouts, and check-ins, and to retrieve daily summaries, history, and settings through MCP tools.

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

MCP server for the Google Health API: heart rate, activity, sleep, SpO2, HRV, ECG and irregular-rhythm notifications, read into a local SQLite cache for fast offline queries and trend analysis. OAuth 2.0 with automatic token refresh, incremental sync, a cache-only offline mode, and a doctor command that diagnoses a setup without spending quota.

An MCP server that converts structured cycling workout specs into MyWhoosh .zwo and Garmin Connect workout files, with tools for validation, description, and rendering. It also includes skills for uploading workouts to both platforms.

An MCP server that lets Claude plan cycling training in intervals.icu, upload workouts to the calendar, and review planned versus actual outcomes, fitness trends, and power curves.

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.