Skip to main content
Glama
jonnyhaynes

Freestyle Libre MCP Server

by jonnyhaynes

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LIBRE_EMAILNoEmail for libreview.
LIBRE_REGIONNoRegion for libreview (default EU).EU
TERRA_DEV_IDNoDev ID for Terra.
TERRA_API_KEYNoAPI key for Terra.
LIBRE_PASSWORDNoPassword for libreview.
LIBRE_PROVIDERNoProvider: libreview, terra, or thryve.
THRYVE_API_KEYNoAPI key for Thryve.
THRYVE_API_SECRETNoAPI secret for Thryve.
THRYVE_ACCESS_TOKENNoOAuth token for Thryve.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_connectionsA

List all patient connections associated with the logged-in account. Returns patient IDs needed for glucose reading tools.

get_current_glucoseA

Fetch the latest blood glucose reading for a patient. Returns the glucose value in both mg/dL and mmol/L, plus trend direction.

get_glucose_historyA

Fetch historical blood glucose readings for a patient. Returns a time-series of readings ordered oldest-first.

get_glucose_summaryA

Summarise glucose trends over the past 24 hours: time-in-range, average, highs, lows, and standard deviation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
provider-infoDetails about the configured data provider and authentication status

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