A
licenseNot graded
qualityC
maintenanceEnables MCP clients to access LibreLinkUp glucose data, including current readings, 12-hour graphs, and 2-week logbooks for followed patients.
MIT
freestyle-libre-mcp
Related Servers
Alternatives to freestyle-libre-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables clinical teams to list patients with active sharing and read glucose, graph, logbook, and statistics from LibreLink Up, with secure magic-link login and encrypted credentials.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
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables access to FreeStyle Libre glucose data through Claude Desktop, providing current readings, historical data, statistics, and trend analysis from LibreLinkUp accounts with secure credential storage.101MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for accessing glucose readings, charts, logbook, and statistics from LibreLink Up sensors, supporting any MCP client.MIT
TDQS
A4/5.0
Scored across 4 tools
Disambiguation5/5
The four tools target distinct data types: patient list, current reading, 12-hour graph, and 2-week logbook events. Descriptions make boundaries clear, so misselection is unlikely.
Naming Consistency5/5
All names use consistent snake_case with a clear verb_noun pattern (list_patients, get_*). The convention is predictable throughout.
Tool Count5/5
Four tools is well within the ideal 3–15 range and each tool covers a distinct, necessary part of the LibreLinkUp data surface without bloat.
Completeness4/5
Core read workflows are covered (patients, current, recent graph, recent logbook). Minor gaps exist for custom time ranges or deeper historical queries beyond the fixed 12-hour/2-week windows, but agents can work around them.
Maintenance
ActivitySlowing
ResponsivenessNo recent community issues