vitals-mcp
Related Servers
Alternatives to vitals-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that synchronizes Garmin Connect summaries into a local SQLite cache and provides tools to query daily activity, recent activities, and recovery data.MIT
- AlicenseNot gradedqualityBmaintenanceSyncs your own Garmin Personal API data into a local SQLite archive and lets any MCP-capable AI assistant query sleep, HRV, stress, body battery, training and activity trends through natural language, with optional interactive charts. Everything runs locally with your own API key, so private health data stays on your machine.1Apache 2.0
- AlicenseBqualityAmaintenanceDownloads all your Garmin health and fitness data into a local SQLite database and exposes 45 MCP tools for AI analysis, enabling assistants to query sleep, training load, HRV, and more.48134 PyPI164AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceMCP server that mirrors your Garmin data into a personal database and exposes tools for health summaries, training load, muscle readiness, and race analysis, with optional chat-driven insights via stdio or HTTP.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP hosts to query and analyze a local Samsung Health mirror, with tools for status, metadata, inventory, daily summaries, and aggregate analyses, plus optional bounded access to raw records and cloud synchronization.13 PyPI2MIT
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that connects WHOOP data to AI assistants like Claude, Codex, and GitHub Copilot, enabling natural-language queries about recovery, sleep, HRV, strain, workouts, and personal health trends against your own baselines, plus HYROX and triathlon analytics. It runs locally, offers aggregate mode, and includes an interactive chart-first dashboard.4 npmMIT
TDQS
Scored across 8 tools
Tools target distinct resources and actions: daily aggregates, workouts, sleep sessions, raw heart rate, schema, SQL, reports, and sync. Minor overlap exists because get_daily summarizes sleep and get_report aggregates daily/workout data, but descriptions make boundaries clear.
Six read tools follow get_<noun> (get_daily, get_workouts, get_sleep, get_heart_rate, get_schema, get_report), while run_sql and sync are action-oriented exceptions. Mostly consistent, though get_daily is slightly less noun-specific than the others.
Eight tools are well-scoped for a personal vitals and analytics MCP. The set covers core queries, schema inspection, reporting, and ingestion without bloat or obvious redundancy.
The surface covers daily metrics, workouts, sleep, raw HR, arbitrary SQL, schema inspection, reporting, and sync/ingest, leaving no obvious dead ends for read and analytics workflows. Manual CRUD is absent, but the server is designed around exports and recomputation.