mcp-freestyle
Related Servers
Alternatives to mcp-freestyle
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for accessing glucose readings, charts, logbook, and statistics from LibreLink Up sensors, supporting any MCP client.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to query FreeStyle Libre sensor glucose read-only through LibreLinkUp, answering questions about current values, curves, time in range, typical days, lows and highs, and sensor lifespan. It keeps its own history of readings and all sensors worn, since LibreLinkUp only exposes the last 12 hours.MIT
- AlicenseAqualityDmaintenanceProvides real-time Dexcom CGM glucose data to MCP clients via the unofficial Share API, enabling queries like current glucose and recent readings within the last 24 hours.2MIT
- AlicenseNot gradedqualityBmaintenanceConnects 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
- AlicenseAqualityDmaintenanceMCP server for Dexcom CGM glucose data, enabling AI agents to access and analyze continuous glucose monitor readings for health intelligence applications.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables secure access to continuous glucose monitoring data from FreeStyle Libre sensors, with tools for current readings, history, statistics, trends, and sensor info, plus an optional Streamable HTTP deployment behind bearer-token authentication.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one returns the most recent glucose reading, while the other returns a historical series over a requested time range. There is no overlap or ambiguity between them.
Both tool names follow the same 'get_' prefix followed by a descriptive noun (current_glucose, glucose_history). The naming pattern is consistent and predictable.
With only two tools, the server feels thin, but the domain is narrow (reading glucose data from a sensor). The two tools cover the essential operations, making the count borderline but not unreasonable.
The server provides access to both current and historical glucose data, which covers the core read-only functionality for the domain. Minor gaps exist (e.g., no health/sensor status), but the available tools are sufficient for the stated purpose.