MCP Glucose Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Glucose Server what's my current glucose level?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Glucose Server
A Model Context Protocol (MCP) server that provides glucose data query tools to AI assistants like Claude and ChatGPT. Connects to the health-data-storage API to retrieve glucose readings.
π― Purpose
This MCP server acts as a specialized interface between AI assistants and your glucose data. It provides natural language tools for querying glucose levels, trends, and statistics.
Related MCP server: MCP Nightscout
ποΈ Architecture Position
ββββββββββββββββββββββββ
β health-data-storage β
β REST API β
ββββββββββββ¬ββββββββββββ
β HTTP GET
βΌ
ββββββββββββββββ
β mcp-glucose β β YOU ARE HERE
β (MCP Server) β
ββββββββ¬ββββββββ
β MCP Tools
βΌ
βββββββββββββββββ
β Claude/ChatGPTβ
βββββββββββββββββπ§ Available Tools
1. get_glucose_readings
Get glucose readings within a date range.
Parameters:
userId(optional): User identifier (defaults to USER_ID env var)startDate(optional): Start date in ISO 8601 formatendDate(optional): End date in ISO 8601 formatlimit(optional): Maximum number of readings (default: 1000)
Example queries:
"What's my glucose been like today?"
"Show me my glucose readings for the past week"
"Get my glucose levels from October 1st to October 22nd"
2. get_latest_glucose
Get the most recent glucose reading.
Parameters:
userId(optional): User identifier (defaults to USER_ID env var)
Example queries:
"What's my current glucose?"
"What was my last glucose reading?"
"Check my latest blood sugar"
3. get_glucose_stats
Get glucose statistics (count, average, min, max) for a time period.
Parameters:
userId(optional): User identifier (defaults to USER_ID env var)startDate(optional): Start date in ISO 8601 formatendDate(optional): End date in ISO 8601 format
Example queries:
"What's my average glucose this week?"
"Show me my glucose stats for the past month"
"What was my glucose range yesterday?"
π Setup
Prerequisites
Node.js 20+
Access to a deployed
health-data-storageinstanceAPI secret for authentication
Installation
# Install dependencies
npm install
# Build TypeScript
npm run buildConfiguration
Create a .env file (or set environment variables):
STORAGE_API_URL=https://your-storage-api.run.app
API_SECRET=your-api-secret
USER_ID=user@example.com # Optional default userUsage with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"glucose": {
"command": "node",
"args": ["/path/to/mcp-glucose/build/index.js"],
"env": {
"STORAGE_API_URL": "https://your-storage-api.run.app",
"API_SECRET": "your-api-secret",
"USER_ID": "user@example.com"
}
}
}
}Restart Claude Desktop.
Usage with ChatGPT
(ChatGPT MCP support coming soon)
π¬ Example Conversations
Once configured, you can ask Claude:
Simple queries:
"What's my latest glucose?"
{
"value": 95,
"unit": "mg/dL",
"date": "2025-10-22T10:30:00Z",
"source": "Lingo"
}Time range queries:
"Show me my glucose for the past 24 hours"
{
"count": 48,
"readings": [
{ "value": 95, "unit": "mg/dL", "date": "2025-10-22T10:30:00Z", "source": "Lingo" },
...
]
}Statistical queries:
"What's my average glucose this week?"
{
"count": 336,
"average": 98.5,
"min": 75,
"max": 125,
"unit": "mg/dL"
}Analysis queries:
"Analyze my glucose patterns over the last month"
Claude will use the tools to fetch data and provide intelligent analysis of your glucose trends, patterns, and insights.
π Related Projects
health-data-storage: Storage backend that this server queries
health-tracking-app: iOS app that collects the glucose data
mcp-activity: (future) MCP server for activity/exercise data
mcp-nutrition: (future) MCP server for food/nutrition data
π Future Enhancements
Potential additions:
Trend analysis tools: Detect glucose spikes, patterns
Correlation tools: Compare glucose with meals, exercise
Alert tools: Notify when glucose is out of range
Export tools: Generate reports, charts
Multi-user support: Query data for multiple users
π οΈ Development
Local Testing
# Build
npm run build
# Run (will use stdio transport)
npm startThe server runs on stdio (standard input/output) as per MCP specification. Use it with Claude Desktop or the MCP inspector for testing.
Testing with MCP Inspector
npm install -g @modelcontextprotocol/inspector
npx @modelcontextprotocol/inspector node build/index.jsπ License
MIT
Available Tools
3 toolsget_glucose_readingsC
Get glucose/blood sugar readings for a user within a date range. Returns glucose values in mg/dL with timestamps and sources.
Inputs: userId, startDate, endDate, limit.
get_glucose_statsA
Get glucose statistics (count, average, min, max) for a user within a date range. Useful for understanding glucose trends and patterns.
Inputs: userId, startDate, endDate.
get_latest_glucoseA
Get the most recent glucose/blood sugar reading for a user. Returns value, unit, timestamp, and source.
Inputs: userId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_glucose_readings retrieves raw readings, get_glucose_stats provides aggregated statistics, and get_latest_glucose fetches the single most recent reading. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on the specific need.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix and descriptive nouns (readings, stats, latest_glucose). The naming is uniform, predictable, and enhances readability, ensuring agents can easily understand and use the toolset.
With 3 tools, the server is well-scoped for its glucose monitoring purpose, covering key retrieval operations. However, it feels slightly thin as it lacks tools for creating, updating, or deleting glucose data, which might be expected in a full CRUD lifecycle, though this is reasonable for a read-only server.
The toolset is complete for read-only operations, offering raw data, statistics, and the latest reading. However, there are notable gaps in the surface, such as missing create, update, or delete tools, which limits agents to retrieval-only workflows and could cause failures in scenarios requiring data modification.
Related MCP Connectors
Your own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.
Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only.
Glucose readings from your LibreLink Up sensor: graph, logbook, stats and summaries (read-only). Sec
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides access to Dexcom G7 continuous glucose monitor data, enabling AI assistants to retrieve current glucose readings and historical data.14-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Nightscout for real-time glucose monitoring, analysis, and treatment logging, enabling natural language interaction with CGM data.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables reading real-time continuous glucose monitor data from Dexcom sensors via the Share API, allowing Claude to access glucose levels, trends, and statistics.-
- AlicenseBqualityDmaintenanceEnables AI assistants to access and analyze Continuous Glucose Monitor (CGM) data from Nightscout, providing real-time readings, history, and analytics.71MIT