Skip to main content
Glama
Sign In
Dexcom Share MCP Server

Dexcom Share MCP Server

by jeremyclee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Dexcom Share MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-freestyle

      lozit
      A
      license
      A
      quality
      C
      maintenance
      MCP server that reads glucose data from a FreeStyle sensor via the LibreLinkUp API, providing current glucose and history with explicit coverage and gaps.
      2
      39 npm
      MIT

    • libre-mcp

      mskerwiderski
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • 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.
      -
    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.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one returns a set of recent readings over a time window, while the other returns only the single most recent reading. There is no ambiguity about which to use for a given scenario.

    Naming Consistency5/5

    Both tool names use a consistent 'get_adjective_noun' pattern (get_glucose_readings and get_latest_reading), making the naming predictable and easy to understand.

    Tool Count3/5

    With only two tools, the surface feels thin for a glucose monitoring server, but it covers the essential use cases of retrieving current and recent data. The count is reasonable for a focused utility, though it leaves little room for additional functionality.

    Completeness3/5

    The server covers the primary use case of retrieving real-time glucose data. However, it lacks tools for historical retrieval (beyond 24 hours), setting alerts, managing device status, or user authentication, which are common interactions for a Dexcom integration.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources