Skip to main content
Glama
jonnyhaynes

Freestyle Libre MCP Server

by jonnyhaynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Freestyle Libre MCP Server

No user-submitted related servers found.

    Related Servers

    • LibreLink MCP Server

      amansk
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to securely access FreeStyle LibreLink continuous glucose monitoring data, providing real-time readings, historical analysis, and health insights through natural language queries.
      8
      13
      -

    • dexcom-mcp

      sobek34
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading real-time continuous glucose monitor data from Dexcom sensors via the Share API, allowing Claude to access glucose levels, trends, and statistics.
      -

    • PodQuery

      rilhia
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop to query and analyze diabetes data from Omnipod 5 and Glooko through natural language, providing clinical audit and triage insights such as time in range, trends, and bolus analysis.
      12
      MIT

    • MCP Glucose Server

      lucas-1000
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query glucose data from health storage APIs, providing natural language access to glucose readings, trends, and statistics for diabetes management and health monitoring.
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_connections lists patient IDs, get_current_glucose returns a single latest reading, get_glucose_history returns a time-series, and get_glucose_summary provides aggregate stats. There is no overlap between these tools, and their descriptions make the boundaries explicit.

    Naming Consistency5/5

    All tool names follow a consistent get_<resource> pattern: get_connections, get_current_glucose, get_glucose_history, get_glucose_summary. The verbs are uniform and the nouns are descriptive, making the naming predictable and easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for a focused glucose monitoring server, covering the essential read operations without unnecessary bloat. Each tool earns its place, and the count is far below the threshold where confusion would arise.

    Completeness4/5

    The tool surface covers the core glucose data retrieval operations (list patients, current, history, summary) and meets the apparent purpose. A minor gap is the lack of patient metadata beyond IDs, which would require an additional tool to fully contextualize the data, but this does not severely hinder the primary workflow.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources