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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

an hour ago