MCP server for Eight Sleep smart bed control and sleep data access
Eight Sleep MCP has 8 tools with explicit registration and basic schemas, but falls well short of production quality. Tool names follow verb_noun convention (positive), but most descriptions are terse (5-12 words, well below the 10-1024 character baseline). Parameters lack descriptions entirely in the input schemas, required field descriptions are missing from Zod definitions. Output schemas are not documented. No error handling guidance. No pagination support despite tools that could return large result sets. The implementation shows basic competence but lacks the rigor and LLM-optimization patterns expected of production tools.
Get HRV (Heart Rate Variability) data for a specific date
Check if the configured user is currently in bed
Get sleep data for the configured user within a date range
Get sleep score data for a specific date
Get sleep stages data for a specific date
Get current temperature settings for the configured user
Parameter descriptions missing entirely. All 8 tools have input parameters (level, duration, startDate, endDate, date) with no descriptions in the schema definitions. The Zod schema objects in src/index.ts define types only, not descriptions. LLMs cannot determine when to use 'level' vs 'duration', or what date format is actually required.
Tool descriptions are too terse (5-12 words). Baseline for production tools is 10-1024 characters; these are 30-60 characters and lack WHEN/WHY context. E.g. 'Get sleep data for the configured user within a date range' does not explain what sleep data includes, whether it aggregates across multiple nights, or what the typical use case is.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 40 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 31 | - | v1 |
Get a list of connected Eight Sleep users
Set temperature for the configured user
Output schemas not documented. No tool declares what fields the response contains. An LLM calling getUsers() does not know whether the response contains user_id, email, name, or any other field. This forces the agent to blindly consume responses and invites downstream errors when chaining tools.
No error handling or recovery guidance. Error handling in src/index.ts catches errors and logs them, but responses do not include actionable recovery hints. If authentication fails or a user ID is invalid, the agent receives a generic error with no guidance on next steps.
No pagination or result limits. getSleepData can retrieve data across arbitrary date ranges, potentially returning hundreds or thousands of records. No limit parameter, no pagination guidance, no total_count or next_cursor. Large result sets blow context windows and waste tokens.
Parameter naming lacks type suffixes. 'date' parameter appears in 4 tools with no disambiguation. 'level' in setTemperature lacks a suffix (temperature_level?) and units are not specified (Celsius, Fahrenheit, or arbitrary scale?). This forces LLMs to guess at parameter semantics.
Date format undocumented. getSleepData, getHrv, getSleepScore, and getSleepStages all accept 'date' or date range parameters described as 'YYYY-MM-DD format' in the provided spec, but this format constraint is NOT visible in the Zod schema or descriptions in src/index.ts. The LLM must infer it.
Required credentials exposed in config. src/config.ts loads EIGHT_SLEEP_EMAIL, PASSWORD, CLIENT_ID, and CLIENT_SECRET from environment variables and stores them in a config object that could be logged or inspected. While the server uses the token-based auth internally, the raw credentials are accessible at runtime.