No. This MCP works through Whoop's private iOS API, which isn't a public surface they intend for third-party tools. Whoop's terms reserve the right to take action against accounts they catch using unsupported integrations — realistically that means suspending API access or terminating the membership. The author has used the MCP heavily for weeks without issue, and traffic patterns look similar to normal app usage, but there's no guarantee. If losing your Whoop account would be a problem for you, don't use this.
It's 13 endpoints, all read-only, no journal, no strength, no stress, no coach, no smart alarm, no trends beyond a single recovery score per day. Whoop also pulled numeric `sport_id` past 2025-09-01 (now `sport_name` strings only). If you only need recovery score + sleep stage totals + workout list, the OAuth API is the right answer.
Yes — the API doesn't care which strap you have. It cares about your account.
When it launches and the iOS app updates, the api version may bump from 7 to 8. The MCP's `constants.ts` may need an update. Worst case, projections break and you fix them.
Sure. The MCP doesn't care where it runs. Just make sure your `.env` survives restarts.
Each user needs their own `.env` with their own Whoop credentials. Don't share tokens.
whoop-mcp 是一款TypeScript开发的AI辅助工具。开源MCP工具：Model Context Protocol server giving Claude (or any MCP client) full read + writ。⭐5 · TypeScript 主要应用场景包括：提供MCP服务。