Unofficial Eight Sleep MCP server: read sleep trends, temperature, alarms; gated pod control.
Unofficial Eight Sleep MCP server: read sleep trends, temperature, alarms; gated pod control. The eight mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
eight_sleep_nightly_summary — Multi-night summary: best night, worst night, mean score, nights under 70 / over 85 — one call instead of post-processing raw get_trendseight_sleep_wellness_context — Returns a normalized delx-wellness-context/v1 payload so other Delx Wellness tools (Nourish, Exercise Catalog, Telegram coaches) can read sleepAction — Tooldelx-wellness-hermes on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 3 environment variables: EIGHT_SLEEP_TOKEN_PATH, EIGHT_SLEEP_CLIENT_ID, EIGHT_SLEEP_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Eight's toolset — eight_sleep_nightly_summary, eight_sleep_wellness_context, Action — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| eight_sleep_nightly_summary | Multi-night summary: best night, worst night, mean score, nights under 70 / over 85 — one call instead of post-processing raw get_trends. |
| eight_sleep_wellness_context | Returns a normalized delx-wellness-context/v1 payload so other Delx Wellness tools (Nourish, Exercise Catalog, Telegram coaches) can read sleep context without knowing the Eight Sleep API. |
| Action | Tool |
{
"mcpServers": {
"eight-sleep": {
"command": "npx",
"args": ["-y", "delx-wellness-hermes"],
"env": {
"EIGHT_SLEEP_TOKEN_PATH": "your-value",
"EIGHT_SLEEP_CLIENT_ID": "your-value",
"EIGHT_SLEEP_CLIENT_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| EIGHT_SLEEP_TOKEN_PATH | Credential the server authenticates with. | Yes |
| EIGHT_SLEEP_CLIENT_ID | Configuration value read at startup. | Optional |
| EIGHT_SLEEP_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.