Wellness CGM MCP
Related Servers
Alternatives to Wellness CGM MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Dexcom CGM glucose data, enabling AI agents to access and analyze continuous glucose monitor readings for health intelligence applications.10MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read and analyze Dexcom CGM data through tools for current glucose, recent historical readings, and glucose statistics such as time in range.3MIT
- AlicenseAqualityDmaintenanceBridges your Nightscout CGM data with AI assistants via the Model Context Protocol, enabling natural language queries about glucose readings, treatments, statistics, and pattern analysis.21GPL 3.0
- AlicenseNot gradedqualityAmaintenanceConnects CareSens continuous glucose monitor accounts to MCP-capable AI tools such as ChatGPT and Claude, letting users check current glucose readings, past measurement history, and period-based glucose statistics through natural language. It runs as a deployable server that authenticates with a CareSens session and exposes the data over a private MCP endpoint.AGPL 3.0
- AlicenseBqualityAmaintenanceLocal-first MCP server that connects AI agents to your Polar training, sleep, Nightly Recharge and continuous-sample data.3889 npm6MIT
- AlicenseAqualityAmaintenanceMCP server that reads glucose data from a FreeStyle sensor via the LibreLinkUp API, providing current glucose and history with explicit coverage and gaps.243 npmMIT
TDQS
Scored across 19 tools
Each tool targets a distinct aspect: connection status, glucose reading, analytics (hypos, daily summary, TIR, meal response), authentication (Dexcom OAuth, Libre login), profile management, and demo. The overlap between cgm_connection_status and cgm_libre_status is resolved by scope (general vs. Libre-specific), and descriptions clearly differentiate window vs. now, and summary vs. TIR.
All tools follow a consistent cgm_ prefix with snake_case naming. While some are noun-only (cgm_manifest, cgm_demo) and others are verb_noun (cgm_profile_get, cgm_profile_update), the pattern is uniform and predictable, making it easy to infer the resource or action.
19 tools is slightly above the ideal 3-15 range, but the server covers a broad domain: data retrieval, analytics, auth, profile, and demo. Each tool serves a clear purpose, and the count is justified by the comprehensive feature set without being overwhelming (not 25+).
The tool surface covers the full lifecycle: connection status, glucose data (now/window), analytics (hypos, daily summary, TIR, meal response), authentication flows (Dexcom OAuth, Libre login), profile management (get/update/onboarding), and demo/quickstart. There are no obvious dead ends; the only missing piece might be a delete-profile tool, but that's a minor gap and profile update covers modification.