Provider guide · private mobile service
Eight Sleep MCP for AI agents
Give an agent bounded access to nightly trends, temperature schedules, alarms and compatible base state while keeping the first connection read-only and the unofficial upstream boundary explicit.
Short answer
Run npx -y eight-sleep-mcp-unofficial setup, log in locally, verify with npx -y eight-sleep-mcp-unofficial doctor, and start from read-only summaries. There is no supported public developer API behind this connector: private mobile-app endpoints can change without notice. Credentials and tokens stay local, and write tools remain disabled until the user deliberately enables them.
Safe default
- Read sleep trends and the current temperature schedule.
- Keep identifiers redacted in structured responses.
- Inspect connection status, inventory and privacy before personal records.
- Leave pod mutations disabled during initial setup.
Unstable boundary
- The connector follows private mobile-app endpoints, not a supported developer API.
- Endpoint, token or response shapes may change upstream without a migration window.
- Account credentials are more sensitive than a revocable provider OAuth scope.
- This is suitable for a personal integration, not a silent multi-user dependency.
Setup method
Connect Eight Sleep in five controlled steps
- 1
Confirm the account and Pod
Use your own active Eight Sleep account and verify that the official app can see the correct Pod and assigned bed side before configuring another client.
- 2
Run local setup
Run npx -y eight-sleep-mcp-unofficial setup. Enter the same account email and password used by the Eight Sleep app; leave mutations disabled for the first connection.
- 3
Create the local session
Run npx -y eight-sleep-mcp-unofficial login. The package exchanges the credentials for a bearer token and stores it locally with user-only permissions.
- 4
Verify before reading sleep data
Run npx -y eight-sleep-mcp-unofficial doctor, then call eight_sleep_connection_status, eight_sleep_data_inventory and eight_sleep_privacy_audit.
- 5
Begin read-only
Start with eight_sleep_nightly_summary and eight_sleep_get_temperature. Enable a write gate later only for a user-confirmed temperature, side, away-mode or alarm action.
Install, login and verify
npx -y eight-sleep-mcp-unofficial setupnpx -y eight-sleep-mcp-unofficial loginnpx -y eight-sleep-mcp-unofficial doctorMCP client configuration
Add the server only after login and doctor succeed on the same machine.
{
"mcpServers": {
"eight_sleep": {
"command": "npx",
"args": ["-y", "eight-sleep-mcp-unofficial"]
}
}
}What the agent can use
Nightly trends
Scores, sleep stages, presence and normalized multi-night summaries when returned by the account service.
Temperature program
Current level and bedtime, initial-sleep and final-sleep schedule context for the assigned side.
Alarms
Configured alarms and compatible thermal or vibration state, with snooze and dismiss treated as writes.
Device and base
Assigned bed side plus compatible torso and leg angles when an adjustable base returns them.
Safe first-call sequence
- 1. eight_sleep_connection_status
- 2. eight_sleep_data_inventory
- 3. eight_sleep_privacy_audit
- 4. eight_sleep_nightly_summary
- 5. eight_sleep_get_temperature
Two-key mutation gate
Temperature, side state, away mode and alarm actions require both EIGHT_SLEEP_ALLOW_MUTATIONS=true and explicit_user_intent=true on that call. Keep the environment gate off until a concrete write is needed, then confirm the exact action.
Sides, partners and privacy
Eight Sleep's current privacy notice says each linked user can control their own side and that linked partners can see each other's sleep, biometric and temperature data. Confirm the selected user and side before reading or changing state. The connector redacts email, device serial, address and payment identifiers from normal responses, but household sharing configured in the official service remains a separate upstream privacy choice.
Eight Sleep MCP questions
What is the Eight Sleep MCP server?
eight-sleep-mcp-unofficial is a local-first connector for sleep trends, temperature schedules, alarms and compatible adjustable-base state. It translates the mobile-app service into bounded MCP tools for an AI agent.
Does Eight Sleep offer a supported public developer API for this connector?
No supported public developer API is used by this project. The unofficial connector follows private mobile-app endpoints, which can change without notice. Treat it as a personal integration with a higher maintenance risk than an official OAuth API.
Where are my Eight Sleep credentials stored?
Credentials and tokens stay local on the machine running the MCP server. Setup stores the account configuration and token files with user-only permissions; sensitive identifiers are redacted from normal tool responses.
Can an agent change my Pod temperature or alarms?
Not by default. Reads work without the write gate. A mutation requires EIGHT_SLEEP_ALLOW_MUTATIONS=true and explicit_user_intent=true on the individual call, so enabling the environment flag alone does not authorize an unconfirmed change.
Can this MCP read raw live sensors or Bluetooth data?
No. Continuous biometric sensor streams and BLE are not available through this connector. It uses the account-level sleep, schedule, alarm and device records returned by the mobile-app service.
Is Eight Sleep MCP medical advice?
No. Sleep scores, temperature settings and biometric summaries are wellness context. This connector is not medical advice, diagnosis, treatment, emergency monitoring or a substitute for a qualified clinician.
Canonical and official sources
Delx Wellness and eight-sleep-mcp-unofficial are not affiliated with Eight Sleep. This page provides technical wellness integration context, not medical advice.