Mi Fitness Data Bridge runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 8 Sep 2026.
Local-first bridge: export your own Mi Fitness (Xiaomi) health data to SQLite/JSON/CSV and MCP.
Today is the operative word: we check Mi Fitness Data Bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
MCP server for the Withings Health API with OAuth, local SQLite cache, and trend analysis.
MCP server for the Google Health API, with a local SQLite cache and trend analysis.
Sync your whole Datto BCDR fleet into local SQLite and answer the questions the per-appliance
Local-first Garmin data warehouse: sync once to SQLite, analyze trends and correlations offline.
A local memory engine. You own the SQLite file. Not Mem0's hosted OpenMemory MCP.
Local-first AI memory cartridge with persistent MCP memory for Claude via SQLite FTS5.
Your health data (weight, macros, weigh-ins) as MCP tools — in your own Supabase, zero custody.
Answers built from our own checks of this server.