Skip to main content
Glama
amansk

LibreLink MCP Server

by amansk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to LibreLink MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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.
      -

    • Garmin Health MCP Server

      eversonl
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to access and analyze Garmin wearable health data including sleep, HRV, Body Battery, and activity metrics. Users can query their health trends, track recovery, and generate interactive HTML dashboards using natural language.
      9
      6
      MIT
    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.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes: current glucose, history, stats, trends, sensor info, credentials, ranges, and connection validation. However, get_glucose_stats and get_glucose_trends both perform analysis on glucose data and could be confused by an agent, though their descriptions clarify the difference.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_* for data retrieval, configure_* for setup, and validate_connection for testing. No mixed conventions or inconsistent verb styles.

    Tool Count5/5

    The 8 tools are well-scoped for a glucose monitoring server. Each tool addresses a distinct need: current reading, history, statistics, trends, sensor information, credential setup, range configuration, and connection validation. No redundant or unnecessary tools.

    Completeness4/5

    The tool set covers core glucose monitoring workflows: reading current values, retrieving history, calculating stats, analyzing trends, and checking sensor status. Configuration and connection validation are also included. A minor gap is the lack of a tool to filter history by specific time ranges, but the default 24-hour window is likely sufficient for most use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources