Dexcom G7 MCP Server

Created By
phildoughertya year ago
MCP server for getting your blood glucose readings and history using dexcom share
Overview

what is Dexcom G7 MCP Server?

Dexcom G7 MCP Server is a Model Context Protocol (MCP) server that provides access to continuous glucose monitor data from the Dexcom G7 device, allowing users to retrieve current glucose readings and historical data.

how to use Dexcom G7 MCP Server?

To use the server, you can deploy it using Docker or MCP-Compose with your Dexcom account credentials. After setting up, you can make HTTP requests to retrieve glucose data.

key features of Dexcom G7 MCP Server?

  • Current Glucose Reading: Access the latest glucose value with trend information.
  • Historical Data: Retrieve glucose readings for a specified time period.
  • Dual Units: Values provided in both mg/dL and mmol/L.
  • HTTP Transport: Easy integration with a native HTTP/JSON-RPC interface.
  • MCP Compatible: Full compliance with the Model Context Protocol.

use cases of Dexcom G7 MCP Server?

  1. Integrating glucose monitoring into health applications.
  2. Providing real-time glucose data to AI assistants.
  3. Analyzing historical glucose trends for better health management.

FAQ from Dexcom G7 MCP Server?

  • Can I use this server without a Dexcom account?

No, a valid Dexcom account with data sharing enabled is required.

  • Is the server free to use?

Yes, the server is open-source and free to use.

  • What should I do if I encounter authentication issues?

Verify your Dexcom username and password, and ensure data sharing is enabled in your account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
phildougherty
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago