Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Descripción del creador (original en inglés)
Read-only FreeStyle glucose sensor access via LibreLinkUp. Not a medical device.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD, LIBRELINKUP_VERSION, LIBRELINKUP_PRODUCT, LIBRELINKUP_BASE_URLLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu 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-freestyleCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
LIBRELINKUP_VERSION envLIBRELINKUP_PRODUCT envLIBRELINKUP_BASE_URL envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub lozit, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: LIBRELINKUP_EMAIL, LIBRELINKUP_PASSWORD
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.4) llegó al registro hace 3 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Mirobody, FHIR MCP Server, Google Health MCP
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
A Model Context Protocol server that reads data from a FreeStyle glucose sensor.
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:
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.
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
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.
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.
| 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 |
| 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.
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/
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.
README.md — this fileCLAUDE.md — instructions for Claude Codedocs/ — project documentation (architecture, decisions, learnings)intake/ — upstream notes and raw specsdocs/media/ — visual assetsdocs/VISION.mddocs/ARCHITECTURE.mddocs/decisions/docs/LEARNINGS.mddocs/GLOSSARY.mddocs/DATA_MODEL.mddocs/SECURITY.mddocs/ROADMAP.mdNot 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.
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.
raw_trend_arrow rather than guessed at — a confidently wrong arrow is worse than none.Report vulnerabilities privately to guillaume.ferrari@protonmail.com — see docs/SECURITY.md.
MIT © Guillaume Ferrari