Eight Sleep Mcp
Let an agent read Eight Sleep trends, temperature, and alarms—and optionally control the pod when mutations are explicitly enabled.
Overview
Eight Sleep MCP is a MCP server for the Build phase that lets agents read—and optionally control—Eight Sleep pod sleep, temperature, and alarm data through an unofficial stdio integration.
What is this MCP server?
- Read sleep trends, pod temperature, and alarms via unofficial Eight Sleep MCP (v0.2.5)
- Default read-only; write tools (temperature, side, away mode, alarms) require EIGHT_SLEEP_ALLOW_MUTATIONS=true
- Setup command can store credentials in ~/.eight-sleep-mcp/config.json (chmod 600) instead of client env
- Privacy modes: summary, structured, or raw via EIGHT_SLEEP_PRIVACY_MODE
- Package version 0.2.5 on npm identifier eight-sleep-mcp-unofficial
- Default mutation policy: read-only unless EIGHT_SLEEP_ALLOW_MUTATIONS is true
- Credentials optionally stored at ~/.eight-sleep-mcp/config.json with chmod 600 per setup docs
Community signal: 2 GitHub stars.
What problem does it solve?
You want your agent to reason over real Eight Sleep data without hand-rolling API clients and risking uncontrolled pod changes.
Who is it for?
Builders with an Eight Sleep pod who want a guarded MCP layer for personal automation or wellness-side projects.
Skip if: Anyone without Eight Sleep hardware or teams that need vendor-supported official APIs and SLAs for a commercial health product.
What do I get? / Deliverables
After setup, your agent can query sleep trends and pod state read-only by default, with explicit opt-in for mutation tools.
- MCP tools for sleep trends, temperature, and alarms
- Optional gated pod control and alarm snooze/dismiss when mutations enabled
Recommended MCP Servers
Journey fit
Hardware and wellness API wiring happens when you integrate external services into an agent or app, which is build-phase work. Eight Sleep is a third-party API integration with OAuth-style setup and gated writes, fitting the integrations subphase rather than core frontend or backend scaffolding.
How it compares
Unofficial consumer hardware MCP integration, not a clinical health records or FHIR server.
Common Questions / FAQ
Who is Eight Sleep MCP for?
Eight Sleep owners and indie developers wiring personal or experimental health agents who accept an unofficial community MCP server.
When should I use Eight Sleep MCP?
Use it during build integrations when your agent or app needs live sleep and pod telemetry, keeping mutations disabled until you trust automation.
How do I add Eight Sleep MCP to my agent?
Install eight-sleep-mcp-unofficial from npm, run the setup flow to store credentials under ~/.eight-sleep-mcp/, register stdio MCP in your client, and set EIGHT_SLEEP_ALLOW_MUTATIONS only if you need write tools.