MCP Freestyle

Name: MCP Freestyle
Author: lozit

by lozitversion 0.1.4i★ –iRuns on your computer

Registry nameio.github.lozit/mcp-freestyle

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health
You need to fill in: LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD, LIBRELINKUP_VERSION, LIBRELINKUP_PRODUCT, LIBRELINKUP_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "freestyle": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-freestyle"
      ],
      "env": {
        "LIBRELINKUP_EMAIL": "your-value",
        "LIBRELINKUP_PASSWORD": "your-value",
        "LIBRELINKUP_VERSION": "your-value",
        "LIBRELINKUP_PRODUCT": "your-value",
        "LIBRELINKUP_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add freestyle --env LIBRELINKUP_EMAIL=your-value --env LIBRELINKUP_PASSWORD=your-value --env LIBRELINKUP_VERSION=your-value --env LIBRELINKUP_PRODUCT=your-value --env LIBRELINKUP_BASE_URL=your-value -- npx -y mcp-freestyle

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "freestyle": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-freestyle"
      ],
      "env": {
        "LIBRELINKUP_EMAIL": "your-value",
        "LIBRELINKUP_PASSWORD": "your-value",
        "LIBRELINKUP_VERSION": "your-value",
        "LIBRELINKUP_PRODUCT": "your-value",
        "LIBRELINKUP_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "freestyle": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-freestyle"
      ],
      "env": {
        "LIBRELINKUP_EMAIL": "your-value",
        "LIBRELINKUP_PASSWORD": "your-value",
        "LIBRELINKUP_VERSION": "your-value",
        "LIBRELINKUP_PRODUCT": "your-value",
        "LIBRELINKUP_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

LIBRELINKUP_EMAIL required env
LibreLinkUp *follower* account e-mail — not the primary LibreLink account. The password is stored once via `npx mcp-freestyle-login` in the OS keychain, so it never appears in this configuration.
LIBRELINKUP_PASSWORD secret env
Overrides the OS keychain. Intended for CI and one-off runs; prefer `mcp-freestyle-login` so no credential lands in a config file.
LIBRELINKUP_VERSION env
Pinned LibreLinkUp client version sent as the `version` header. Upstream rejects stale values — set this to the current LibreLinkUp app version if requests start failing.
LIBRELINKUP_PRODUCT env
Client product identifier sent as the `product` header.
LIBRELINKUP_BASE_URL env
Entry point for authentication. The regional host is discovered at login and is never configured here.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account lozit, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 1022 servers in this category
Published to the registry more recently than 30% of the other 1022 servers in this category
Basic checks equal to or better than 100% of the other 1022 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Freestyle safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated today

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-freestyle

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

npm install -g mcp-freestyle

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

git clone https://github.com/lozit/mcp-freestyle.git && cd mcp-freestyle

npm install && npm run build

2. Log in once

npm run login          # from a clone

mcp-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:

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:

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

Variable	Required	Default	Notes
`LIBRELINKUP_EMAIL`	yes	—	Your LibreLinkUp follower account, not the primary LibreLink one
`LIBRELINKUP_PASSWORD`	no	keychain	Overrides the keychain. For CI or a one-off run — not the expected path
`LIBRELINKUP_VERSION`	no	`4.16.0`	Pinned client version. Upstream rejects stale values — if requests start failing, set this to the current LibreLinkUp app version
`LIBRELINKUP_PRODUCT`	no	`llu.android`
`LIBRELINKUP_BASE_URL`	no	`https://api.libreview.io`	Entry point only; the regional host is discovered at login

Tools

Tool	What it returns
`get_current_glucose`	The 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_history`	Readings 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

npm test          # Node's built-in test runner — no build step needed

npm run typecheck # strict TypeScript, the project's only lint gate npm 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

Vision: docs/VISION.md
Architecture: docs/ARCHITECTURE.md
Decisions: docs/decisions/
Learnings: docs/LEARNINGS.md
Glossary: docs/GLOSSARY.md
Data model: docs/DATA_MODEL.md
Security & privacy: docs/SECURITY.md
Roadmap: docs/ROADMAP.md

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.

npm test          # Node's built-in runner, no network — `fetch` is injectable

npm 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 guillaume.ferrari@protonmail.com — see docs/SECURITY.md.

MCP Freestyle

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

mcp-freestyle

Requirements

Quickstart

1. Install

2. Log in once

3. Hook it up to Claude

Configuration

Tools

Development

Usage

Project structure

Documentation

Disclaimer

Contributing

Known gaps

Security

License