Nightscout

Install

Pin version unavailable — hosted endpoints aren’t versioned

Hosted endpoint (OAuth + Nightscout token)
https://nightscout.b77.ai/mcp

Setup by client

Pick your client — the config below is generated for this server (hosted endpoint). Copy respects the “Pin version” switch above.

https://nightscout.b77.ai/mcp

claude mcp add --transport http nightscout https://nightscout.b77.ai/mcp

{
  "mcpServers": {
    "nightscout": {
      "url": "https://nightscout.b77.ai/mcp"
    }
  }
}

{
  "servers": {
    "nightscout": {
      "type": "http",
      "url": "https://nightscout.b77.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "nightscout": {
      "serverUrl": "https://nightscout.b77.ai/mcp"
    }
  }
}

Environment variables

Defined in the server's official registry manifest. Required secrets are shown as <YOUR_…> placeholders in the configs above.

• Authorization header — No API key: sign in with your B77 account (OAuth) during connector setup and provide your Nightscout URL + token in the app. Access is scoped to your account and is read-only. Get it: b77.ai app sign-in / your Nightscout site settings

Official version check

What it can do

• Read-only glucose readings from your Nightscout URL (current value, trend data)
• No write actions — the connector never changes anything in the connected tool

Common issues

Connector asks to sign in

Setup is OAuth-based: open the app page, click Install, copy the connection URL, paste it as a custom connector, then sign in with your B77 account. Source: b77.ai/apps/nightscout ↗

No glucose data appears

Check the Nightscout URL and token you supplied in the app flow — the connector reads directly from your Nightscout site and stores nothing on B77 servers. Source: b77.ai/apps/nightscout ↗

Alternatives

• Apple Health
• Google Health Mcp
• Bluetooth LE Health Sensors

Last verified: 2026-10-15 ｜ Sources: B77 Nightscout app page ↗

About this server