mcp-server-dexcom-health
Related Servers
Alternatives to mcp-server-dexcom-health
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first CGM MCP for AI agents: Dexcom Developer API and FreeStyle Libre via LibreLink Up.1924 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes health metrics from the Sapphire Wellness App to AI assistants, enabling natural language queries for activity, blood pressure, glucose, heart rate, sleep, and SpO2 data.-
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server that connects Claude to your personal Dexcom CGM (Continuous Glucose Monitor) for assistive diabetes management intelligence.MIT
- AlicenseAqualityAmaintenanceOpen-source MCP server for MetricBridge (formerly Health Export AI). 16 tools and 22 prompts let any MCP agent query 190 Apple Health metrics from files on your own machine. The server is read-only, has zero dependencies and makes zero network calls.16389 npm8MIT
- AlicenseAqualityDmaintenanceAn MCP server that locally authenticates with Google Health API v4 and provides read-only access to Fitbit, Pixel Watch, and other health data for AI agents.2956 npm19MIT
- AlicenseBqualityAmaintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.26301 npm72MIT
TDQS
Scored across 10 tools
Most tools target distinct functions (current, history, stats, summary, episodes, details, time analysis, alerts, export, AGP). However, get_status_summary overlaps with get_statistics and get_current_glucose, and get_episode_details overlaps with detect_episodes, though descriptions clarify the different purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_current_glucose, detect_episodes, analyze_time_blocks, check_alerts, export_data). No mixed conventions or vague verbs.
10 tools is well-scoped for a CGM health analytics server. Each tool serves a distinct analytical or data-access purpose, and the count fits the typical 3-15 range comfortably.
The server covers current readings, historical data, statistics, summaries, episode detection/details, time-of-day analysis, alert checks, data export, and AGP reports. Minor gaps exist such as no tool for managing alert thresholds or user preferences, but for a read-only glucose analyzer, the coverage is strong.