
Eight Sleep Mcp
io.github.davidmosiahPublished by GitHub account davidmosiahv0.2.5Updated Oct 24, 2026
Unofficial Eight Sleep MCP server: read sleep trends, temperature, alarms; gated pod control.
Overview
Unofficial local MCP server that lets an assistant read your Eight Sleep sleep trends, temperature schedule, alarms and base, with optional gated pod control.
- What you can do
- Check connection status and read account, user and current device details
- Read the smart temperature program, sleep trends and alarms, and inspect the adjustable base
- Produce multi-night summaries (best/worst night, mean score) and a normalized wellness context payload
- Optionally, when explicitly enabled, set heating level, turn a side on or off, toggle away mode, and snooze or dismiss alarms
- Audit the current privacy posture without exposing secrets
- When to use it
- Useful if you own an Eight Sleep pod and want an assistant to explain your sleep scores, review the temperature schedule, or adjust pod settings overnight. It is a personal-use connector, not a general sleep-data platform.
- Requirements
- Runs locally via npx (Node.js) over stdio, with optional loopback-only HTTP. Needs an Eight Sleep account: email and password, set through the setup command or the EIGHT_SLEEP_EMAIL and EIGHT_SLEEP_PASSWORD variables. Optional overrides include EIGHT_SLEEP_CLIENT_ID, EIGHT_SLEEP_CLIENT_SECRET, EIGHT_SLEEP_TOKEN_PATH and EIGHT_SLEEP_PRIVACY_MODE. Network access to Eight Sleep endpoints is required.
Installation
In SourceWeft
- Open Eight Sleep Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
[npm version] [npm downloads] [License MIT] [Site]
[GitHub stars] [Built for MCP] [Hermes one-command setup] [Eight Sleep]
⚡ 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:
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
Then add this to your MCP client config:
For Claude Desktop, run setup --client claude and the snippet is written for you.
Try it with your agent
Three things to ask first:
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.jsonwithchmod 600. - Auth tokens stored in
~/.eight-sleep-mcp/tokens.jsonwithchmod 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
- 📨 [email protected] — 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:
Copy skill/SKILL.md into your agent skills dir.
Source: README.md at commit 63fc296
Tools
0Version history
1- v0.2.5LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts