Wellness Cgm Mcp
Connect an AI health or coaching agent to continuous glucose data from Dexcom and FreeStyle Libre without writing both vendor integrations yourself.
Overview
Wellness CGM MCP is an MCP server for the Build phase that lets AI agents read Dexcom and FreeStyle Libre CGM data through a local stdio integration.
What is this MCP server?
- Local-first CGM MCP (npm wellness-cgm-mcp v0.4.0) over stdio transport
- Dexcom Developer API support alongside FreeStyle Libre via LibreLink Up
- Designed for AI agents that reason over glucose trends and alerts
- Runs on your machine to keep health credentials out of cloud-only chat logs
- Published from davidmosiah/wellness-cgm-mcp with connector docs on wellness.delx.ai
- Package version 0.4.0 with registry identifier wellness-cgm-mcp
- Two CGM integration paths: Dexcom Developer API and FreeStyle Libre via LibreLink Up
- stdio MCP transport per modelcontextprotocol server schema 2025-12-11
Community signal: 1 GitHub stars.
What problem does it solve?
Building a glucose-aware agent means duplicating OAuth and vendor-specific CGM APIs for Dexcom and LibreLink Up without a shared MCP surface.
Who is it for?
Solo builders prototyping AI wellness or diabetes-support agents who need both Dexcom and Libre CGM paths behind one MCP server.
Skip if: Clinical deployments that require formal compliance review, or builders who only need manual CSV imports without live CGM APIs.
What do I get? / Deliverables
After registering wellness-cgm-mcp, your agent can query CGM-oriented tools locally so health coaching or logging flows use live sensor context.
- MCP tool access to CGM data sources (Dexcom and Libre paths)
- Agent-callable glucose context for coaching or logging workflows
- Local runtime for wellness connector experiments
Recommended MCP Servers
Journey fit
CGM bridges are built when you are wiring real-world APIs into an agent product, which is core Build-phase integration work. Integrations is the shelf for MCP servers that pull live sensor APIs into agent tool surfaces.
How it compares
Vendor CGM MCP bridge, not a medical device app or a generic fitness tracker skill.
Common Questions / FAQ
Who is Wellness CGM MCP for?
Developers building local-first AI health agents who want Dexcom and FreeStyle Libre glucose data exposed as MCP tools.
When should I use Wellness CGM MCP?
Use it during build and integrations when your agent product needs live CGM reads and you are wiring Dexcom or LibreLink Up credentials on your own hardware.
How do I add Wellness CGM MCP to my agent?
Install the npm package wellness-cgm-mcp, add it as a stdio MCP server in your agent client, and complete Dexcom developer and LibreLink Up setup per the repository and wellness.delx.ai connector documentation.