Skip to main content
Glama
lozit

mcp-freestyle

by lozit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-freestyle

No user-submitted related servers found.

    Related Servers

    • GlucoBridge

      taejeong1126
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects 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

    • LibreLink MCP Server

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

    • Dexcom MCP Server

      cykj40
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server that connects Claude to your personal Dexcom CGM (Continuous Glucose Monitor) for assistive diabetes management intelligence.
      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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    Both tool names follow the same 'get_' prefix followed by a descriptive noun (current_glucose, glucose_history). The naming pattern is consistent and predictable.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources