Eight Sleep MCP

Give your AI agent your Eight Sleep sleep trends, temperature program and alarms — and optionally let it tune the pod overnight.
Local-first MCP server — credentials never leave your machine.

⚡ One-command install with Delx Wellness for Hermes: npx -y delx-wellness-hermes setup — preconfigures this connector alongside the rest of the wellness catalog.

Or wire it standalone into Claude Desktop / Cursor / OpenClaw / any MCP client — see the install section below.

---

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y eight-sleep-mcp-unofficial --http
# GET  http://127.0.0.1:3000/health
# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: EIGHT_SLEEP_MCP_HOST, EIGHT_SLEEP_MCP_PORT, EIGHT_SLEEP_MCP_TRANSPORT=http.

Local-first MCP server that connects AI agents to your Eight Sleep pod — sleep sessions, temperature program, alarms, adjustable base — with an explicit mutation gate for write actions.

Unofficial project. Not affiliated with, endorsed by, or supported by Eight Sleep, Inc. Eight Sleep is a trademark of its respective owner. Use this only with your own Eight Sleep account.

Eight Sleep does not publish a stable public API. This package talks to the same private endpoints (auth-api.8slp.net, client-api.8slp.net, app-api.8slp.net) the mobile app uses, following the path well documented by upstream community projects (lukas-clarke/eight_sleep, mezz64/pyEight, steipete/eightctl).

Part of Delx Wellness — a registry of local-first wellness MCP connectors.

If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.

Why this exists

Eight Sleep ships great sleep telemetry — nightly score, presence intervals, tnt, smart-temperature schedule — but it lives inside a closed iOS/Android app with no public API. Bringing it into your agent today means reverse-engineering OAuth, juggling token refresh, normalizing endpoint shapes, and handling timezone quirks.

This package does all of that locally, exposes Eight Sleep through the Model Context Protocol, and lets any MCP-compatible agent read your sleep context (and write pod commands, if you opt in) with one config snippet. Credentials and tokens stay on your machine.

Setup in 60 seconds

npx -y eight-sleep-mcp-unofficial setup   # interactive: email + password
npx -y eight-sleep-mcp-unofficial login   # persists the auth token
npx -y eight-sleep-mcp-unofficial doctor  # verifies you're ready

Then add this to your MCP client config:

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

For Claude Desktop, run setup --client claude and the snippet is written for you.

Try it with your agent

Three things to ask first:

Use eight_sleep_connection_status to check setup, then run eight_sleep_get_me.
Tell me what device you find.

Call eight_sleep_get_trends for the last 7 days, response_format=json.
What's my best night and worst night, and why?

Call eight_sleep_get_temperature. Summarize the current smart schedule
(bedtime, initial sleep, final sleep) and tell me if I should tune it.

Data availability

This package talks to the Eight Sleep mobile-app API. It does not access continuous biometric sensor streams or BLE.

Workflow tools

Mutation tools (write gate)

Off by default. To enable, re-run setup with --allow-mutations or enable EIGHT_SLEEP_ALLOW_MUTATIONS. Do not put the assignment in default MCP snippets.

When the gate is off, mutation tools return an explicit mutations disabled error so agents can detect it and ask the user to opt in.

Privacy

• Credentials stored in ~/.eight-sleep-mcp/config.json with chmod 600.
• Auth tokens stored in ~/.eight-sleep-mcp/tokens.json with chmod 600.
• Sensitive fields (email, device serial, shipping address, payment last-four) are redacted from tool responses by default.
• EIGHT_SLEEP_PRIVACY_MODE:
  • summary — minimal fields only.
  • structured (default) — preserves complete nested sleep fields and future upstream additions while redacting identifiers.
  • raw — full upstream payload (debugging only).

Trend requests validate real YYYY-MM-DD dates, range order and IANA timezone names before any network call.

Call eight_sleep_privacy_audit at any time to inspect the current posture without exposing secrets.

Environment variables

Stability

Eight Sleep changes mobile-app endpoints without notice. This connector tracks upstream community projects (lukas-clarke/eight_sleep, steipete/eightctl, mezz64/pyEight) for breakage signals. If a tool starts returning 4xx unexpectedly, check those repos and the project issues for the latest known-good shape.

Credits

• lukas-clarke/eight_sleep — Home Assistant integration, most current reference for V2 endpoints.
• mezz64/pyEight — original Python library; auth + endpoint discovery.
• steipete/eightctl — CLI variant with extracted client credentials.
• LiamSnow/opensleep — full open-source firmware (deeper than this MCP goes).

📧 Contact & Support

• 📨 support@delx.ai — general questions, integration help, partnerships
• 🐛 Bug reports / feature requests — GitHub Issues
• 🐦 Updates — @delx369 on X
• 🌐 Site — wellness.delx.ai

License

MIT — see LICENSE.

Skill or MCP

Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:

npx -y eight-sleep-mcp-unofficial call eight_sleep_connection_status --json '{}'

Copy skill/SKILL.md into your agent skills dir.