Mcp Freestyle

io.github.lozitPublished by GitHub account lozitv0.1.4Updated Oct 24, 2026

Read-only FreeStyle glucose sensor access via LibreLinkUp. Not a medical device.

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Read-only MCP server that lets an assistant fetch current and recent glucose readings from a FreeStyle sensor via the LibreLinkUp cloud.

What you can do
Read the latest glucose measurement with the time it was actually taken and the account's target band, never presented as a live reading. Retrieve readings from the last N hours (max 12) with time-in-range, the range actually covered, a truncated flag and listed collection gaps. Answer plain-language questions about current glucose, time in range today, or the last few hours.
When to use it
Useful if you already share FreeStyle sensor data through the LibreLink app to a LibreLinkUp follower account and want an assistant to summarize recent glucose readings and time in range. Not for anyone using a standalone reader, since nothing is uploaded continuously.
Requirements
Local process run with npx; Node.js 20 or newer and a working OS keychain (macOS Keychain, Windows Credential Manager, or libsecret on Linux). A FreeStyle sensor read by the LibreLink app with LibreLinkUp sharing to a follower account. LIBRELINKUP_EMAIL is required; optional LIBRELINKUP_PASSWORD, LIBRELINKUP_VERSION, LIBRELINKUP_PRODUCT and LIBRELINKUP_BASE_URL. Network access to Abbott's cloud. Desktop only.
Before you install
Signs in to the unofficial, unsupported LibreLinkUp/LibreView API, which can stop working without notice. The follower account password is stored in the OS keychain by the login command; LIBRELINKUP_PASSWORD overrides it and puts a credential in a config file, so prefer the keychain. The upstream token is not stored and the server re-authenticates. Not a medical device: do not use output for dosing or treatment decisions.

Installation

In SourceWeft

  1. Open Mcp Freestyle in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-freestyle

[CI] [npm] [License: MIT] [Node: ≥20] [Not a medical device]

A Model Context Protocol server that reads data from a FreeStyle glucose sensor.

Requirements

This server reads your data from Abbott's cloud, so it only works if your data already gets there. You need all of the following:

  • A FreeStyle sensor read by the LibreLink app on a phone. If you use a standalone FreeStyle reader instead, nothing is uploaded continuously and this server cannot help you.
  • LibreLinkUp sharing set up from that LibreLink app to a follower account. The server signs in as the follower.
  • Node.js ≥ 20, and a working OS keychain (macOS Keychain, Windows Credential Manager, or libsecret on Linux).

The server talks to the unofficial LibreLinkUp / LibreView API, which is not affiliated with or supported by Abbott. It can stop working without notice. See docs/decisions/0002-data-source-librelinkup.md.

Quickstart

1. Install

bash
npm install -g mcp-freestyle

Or from a clone, if you'd rather read the code first:

bash
git clone https://github.com/lozit/mcp-freestyle.git && cd mcp-freestylenpm install && npm run build

2. Log in once

bash
npm run login          # from a clonemcp-freestyle-login    # if installed globally

You're prompted for your LibreLinkUp follower e-mail and password. The password is verified by actually authenticating — if it's wrong, or sharing isn't set up, you find out now rather than at the first question you ask Claude. It is then stored in your OS keychain, never in a config file.

The token upstream issues is not stored. It lives ~180 days with no revocation path, so keeping it around would be the bigger risk; the server re-authenticates instead.

At the end, login offers to wire the server into Claude Desktop in one step.

3. Hook it up to Claude

Claude Desktop — one command:

bash
mcp-freestyle-install

It merges an entry into ~/Library/Application Support/Claude/claude_desktop_config.json (%APPDATA%\Claude\… on Windows) using absolute paths, backing up any existing config first and leaving your other servers untouched. It refuses to overwrite a config it can't parse. Quit Claude Desktop fully (⌘Q) and relaunch.

Claude Code:

bash
mcp-freestyle-install code   # prints the exact `claude mcp add` command

The written entry contains only your e-mail — an identifier, not a secret. That is the point of the keychain step: a config file that gets synced, backed up, or pasted into a bug report never holds a credential.

To remove the stored password: mcp-freestyle-logout.

Configuration

VariableRequiredDefaultNotes
LIBRELINKUP_EMAILyes—Your LibreLinkUp follower account, not the primary LibreLink one
LIBRELINKUP_PASSWORDnokeychainOverrides the keychain. For CI or a one-off run — not the expected path
LIBRELINKUP_VERSIONno4.16.0Pinned client version. Upstream rejects stale values — if requests start failing, set this to the current LibreLinkUp app version
LIBRELINKUP_PRODUCTnollu.android
LIBRELINKUP_BASE_URLnohttps://api.libreview.ioEntry point only; the regional host is discovered at login

Tools

ToolWhat it returns
get_current_glucoseThe most recent measurement with the instant it was actually taken, plus the account's own target band. Never presented as a live "now" reading.
get_glucose_historyReadings over the last N hours (max 12) with time-in-range. Always states the range it actually covered and flags truncated when upstream returned less than asked. Collection gaps are listed, never interpolated across.

Upstream holds only ~12 hours of detailed data. Longer horizons are a deferred milestone, not a limitation of these tools.

Development

bash
npm test          # Node's built-in test runner — no build step needednpm run typecheck # strict TypeScript, the project's only lint gatenpm run build     # emits dist/

Usage

Once connected, ask in plain language:

What's my glucose right now?

How has my time in range been today?

Show me the last 6 hours.

The answers carry the instant each reading was actually taken, the range the data actually covered, and any collection gaps — so a reply about "today" says how much of today it could see. If you ask for more than upstream holds, it tells you what it got instead of quietly answering over less.

Not a substitute for your reader or your app. This is informational only — see the disclaimer above.

Project structure

  • README.md — this file
  • CLAUDE.md — instructions for Claude Code
  • docs/ — project documentation (architecture, decisions, learnings)
  • intake/ — upstream notes and raw specs
  • docs/media/ — visual assets

Documentation

Disclaimer

Not a medical device. This project is informational only. Do not use its output to make any treatment decision (dosing, correction, therapy adjustment). Always rely on your official reader/app and your care team.

Contributing

Issues and pull requests are welcome — especially from anyone who can help map the TrendArrow values (see below), or who hits a LibreLinkUp region or payload shape this hasn't seen.

bash
npm test          # Node's built-in runner, no network — `fetch` is injectablenpm run typecheck # strict TypeScript, the project's only lint gate

One rule that is not negotiable: never commit a real glucose reading, sensor serial, account identifier, or credential — not in a fixture, not in an issue, not in a screenshot. Tests use synthetic fixtures only. A value paired with a timestamp is a health measurement even with no name attached.

Design decisions live in docs/decisions/ and the verified upstream contract in docs/ARCHITECTURE.md. Read those before changing how readings are fetched or aggregated — several non-obvious upstream behaviours are documented there because they cost real debugging to find.

Known gaps

  • TrendArrow is not translated. Upstream sends an integer; its mapping is undocumented and has only been observed at one value. It is passed through as raw_trend_arrow rather than guessed at — a confidently wrong arrow is worse than none.
  • ~12 hours of history, maximum. Upstream ignores any longer request. See ADR 0003 for the long-term plan.

Security

Report vulnerabilities privately to [email protected] — see docs/SECURITY.md.

License

MIT © Guillaume Ferrari

Source: README.md at commit 8eb5db1

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts