---
title: Eight Sleep MCP for AI Agents: Safe Read-Only Setup
description: Connect Eight Sleep trends, temperature schedules, alarms and base state to an AI agent with local credentials and explicit write gates.
canonical: https://wellness.delx.ai/guides/eight-sleep-mcp-for-ai-agents
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Eight Sleep MCP for AI Agents

The Eight Sleep MCP server exposes sleep trends, temperature schedules, alarms and compatible base state to an MCP agent. It is an unofficial personal integration built on private mobile-app endpoints, not a supported public developer API.

## Short answer

Run <code>npx -y eight-sleep-mcp-unofficial setup</code>, then <code>npx -y eight-sleep-mcp-unofficial login</code>, verify with <code>npx -y eight-sleep-mcp-unofficial doctor</code>, and begin with read-only summaries. Credentials and tokens stay local. Private mobile-app endpoints can change without notice, so treat this as a higher-maintenance boundary than an official OAuth API.

## Setup method

1. Confirm the official Eight Sleep app can see your account, Pod and assigned bed side.
2. Run <code>npx -y eight-sleep-mcp-unofficial setup</code> with mutations disabled.
3. Run <code>npx -y eight-sleep-mcp-unofficial login</code> to create the local token file.
4. Run <code>npx -y eight-sleep-mcp-unofficial doctor</code>, then call <code>eight_sleep_connection_status</code>, <code>eight_sleep_data_inventory</code> and <code>eight_sleep_privacy_audit</code>.
5. Start with <code>eight_sleep_nightly_summary</code> and <code>eight_sleep_get_temperature</code>.

## MCP client configuration

~~~json
{
  "mcpServers": {
    "eight_sleep": {
      "command": "npx",
      "args": ["-y", "eight-sleep-mcp-unofficial"]
    }
  }
}
~~~

## Data availability

- User profile and assigned bed side: available. Email and device serial redacted by default.
- Smart-temperature schedule (bedtime / initial sleep / final sleep): available. Includes currentLevel, currentDeviceLevel and isOn.
- Sleep trends (nightly score, stages, tnt, presence): available. Date-range query against client-api.8slp.net.
- Alarms and recommended next alarm: available. Includes thermal + vibration toggles.
- Adjustable base angle and preset: available. Returns leg/torso angles when the pod has the adjustable base.
- Write tools (temperature, side, away mode, alarm snooze/dismiss): opt_in. Off by default; require EIGHT_SLEEP_ALLOW_MUTATIONS=true.
- Continuous biometric streams or BLE: not_available. Not exposed by the mobile-app API surface.

Continuous biometric sensor streams and BLE are not available through this connector. Returned trends are account-level records, not a clinical or real-time feed.

## Safe first-call sequence

1. <code>eight_sleep_connection_status</code>
2. <code>eight_sleep_data_inventory</code>
3. <code>eight_sleep_privacy_audit</code>
4. <code>eight_sleep_nightly_summary</code>
5. <code>eight_sleep_get_temperature</code>

## Mutation boundary

Temperature, side state, away mode and alarm actions require both <code>EIGHT_SLEEP_ALLOW_MUTATIONS=true</code> and <code>explicit_user_intent=true</code> on the individual call. Reads remain available with the mutation gate off.

## Privacy and linked sides

- Email/password stored locally in ~/.eight-sleep-mcp/config.json (chmod 600).
- Bearer token stored locally in ~/.eight-sleep-mcp/tokens.json (chmod 600).
- Email, device serial, addresses and payment last-four redacted from responses by default.
- Mutations require EIGHT_SLEEP_ALLOW_MUTATIONS=true — agents cannot accidentally change pod state.
- Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 15 Delx Wellness connectors and never uploaded.

Eight Sleep's current privacy notice says each linked user can control their own side and linked partners can view each other's sleep, biometric and temperature data. Confirm the selected user and side before reading or changing state.

## Stability

This project has no supported public developer API to target. Its private mobile-app endpoints can change without notice. A 4xx or missing field may reflect upstream drift rather than a user or agent error.

## Official sources

- Temperature system: https://www.eightsleep.com/bed-cooling-system/
- Alarm features: https://www.eightsleep.com/fs8/
- Privacy notice: https://www.eightsleep.com/ca-fr/legal/privacy/
- Security and privacy architecture: https://www.eightsleep.com/blog/our-commitment-to-security-and-privacy-how-our-systems-work/

## Canonical Delx sources

- Connector specification: https://wellness.delx.ai/connectors/eight-sleep
- Connector comparison: https://wellness.delx.ai/guides/choose-wellness-mcp-connector
- Security model: https://wellness.delx.ai/security
- npm: https://www.npmjs.com/package/eight-sleep-mcp-unofficial
- GitHub: https://github.com/davidmosiah/eight-sleep-mcp

Delx Wellness and eight-sleep-mcp-unofficial are not affiliated with Eight Sleep. This is technical wellness integration context, not medical advice.