MCP Freestyle

Name: MCP Freestyle
Author: lozit

作者：lozit版本 0.1.4i★ –i在你的电脑上运行

注册名称io.github.lozit/mcp-freestyle

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 诊所与健康
你需要填写：LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD, LIBRELINKUP_VERSION, LIBRELINKUP_PRODUCT, LIBRELINKUP_BASE_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

LIBRELINKUP_EMAIL 必填 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 机密 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 lozit 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1022 个服务器的 0%
发布到注册中心的时间比此分类中其他 1022 个服务器的 30% 更新
基础检查结果等于或优于此分类中其他 1022 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP Freestyle 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.4）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

作者：thetahealth

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

在你的电脑上运行★ 1,408Apache-2.0今天更新

安装

FHIR MCP Server

作者：wso2

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

在你的电脑上运行★ 137Apache-2.09天前更新

安装

Google Health MCP

作者：davidmosiah

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

在你的电脑上运行★ 79MIT4个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.