Oura MCP

Oura MCP pulls sleep, readiness, and resilience data from your Oura Ring into Claude. You give it a date range, it returns JSON with heart rate variability, sleep stages, activity scores, and stress markers. The API is straightforward: you authenticate once with a personal access token from Oura's developer portal, then query by day or week. I've used it to analyse sleep patterns after travel and to correlate readiness scores with workout intensity. It's faster than logging into the Oura app and manually transcribing numbers into a spreadsheet. The main use case is personal health journaling. If you're already tracking habits in text files or using Claude to reflect on your routines, this slots in cleanly. You can ask Claude to summarise your last month of sleep efficiency or flag nights where your resting heart rate spiked. It's also useful for habit coaching: pair it with a prompt that compares your readiness score to your planned workouts and adjusts recommendations accordingly. The data is granular enough for serious analysis but not overwhelming. Quirks: the server only fetches data Oura already exposes via its API, so if your ring hasn't synced recently, you'll get stale numbers. There's no write capability, which means you can't log notes or tag events directly through the MCP. You're also limited by Oura's rate limits, though for personal use this rarely matters. The install is a single uvx command, and the token setup is a one-time thing. Who shouldn't bother: if you don't own an Oura Ring, obviously. If you're happy with the Oura app's built-in trends and don't need to cross-reference health data with other workflows, this adds little. It's also overkill if you just want a quick glance at last night's sleep score. But if you're building a personal knowledge system in Claude or experimenting with AI-assisted health coaching, it's a clean, low-friction integration. I'd reach for this when I want to treat my biometric data as queryable context rather than a walled-garden dashboard.