What this actually does
Out of the box, Claude cannot see your Oura Ring data. It has no login to your Oura account and no reach into the Oura app on your phone, where your readiness, sleep stages, and HRV live. If you paste a screenshot of last night's sleep, Claude can read that one image, but it has no memory of your history and no way to pull a trend across a month.
MCP changes that. The Model Context Protocol is an open standard that lets Claude connect to an outside data source through a consistent interface, the way a USB-C port lets any device plug into one socket. When a service runs an MCP server over your Oura data, Claude can request rows from it during a conversation and reason over real numbers instead of guessing.
Wellness Project runs exactly that server. Your ring connects to Wellness Project over Oura's official OAuth flow, its history syncs in, and a single MCP server exposes that synced history to Claude with read-only access. The result is a normal Claude chat that can answer questions about your actual readiness, sleep stages, HRV, and resting heart rate.
How to connect it
Three pieces have to line up: Oura has to reach Wellness Project, the MCP server has to be added to Claude, and then you ask. Each step takes about a minute and the setup is one-time.
Get the Wellness Project app
Download Wellness Project for iPhone or Android with the buttons above, or sign in on the web. Signing in with Apple or Google takes one tap, the account is free during early access, and this is the app that stores your synced history and serves it to Claude and ChatGPT over MCP.
Connect Oura to Wellness Project
In Wellness Project, open integrations and choose Oura. You are sent to Oura official OAuth sign-in, where you log in and approve read access. Your sleep stages, readiness, HRV, and resting heart rate start syncing in. This builds the history the MCP server will later expose. No export, no screenshots.
Understand what MCP is doing
MCP is the standard that lets Claude talk to an outside data source. You are not pasting data into the chat or training a model on it. You are pointing Claude at a server that already holds your synced Oura history and letting it read the specific rows it needs, when it needs them. Nothing is copied in bulk.
Add the MCP server to Claude
In claude.ai, add wellnessproject.ai/api/mcp as a custom connector and authorize it through your Wellness Project account. Claude Desktop syncs the connector from claude.ai.
Ask Claude about your Oura data
Open a chat and ask. "How did my readiness trend this month?" "Did my HRV drop the weeks I slept poorly?" "What was my average resting heart rate last week?" Claude pulls the structured rows from the server and answers from your Oura history rather than a single screenshot or a generic average.
What to ask once it is connected
The connection is only worth it if the questions get better, and they do. Because Claude reads interpreted history rather than tonight's isolated score, the useful prompts are the ones that span time: patterns, baselines, and cause-and-effect across your Oura signals.
Ask how your resting heart rate moved across a stressful month. Ask whether your readiness tracks with the nights you got to bed earlier. Ask Claude to flag the week your HRV and sleep both dropped together. And because the same server reads every device you connect, those answers can pull Oura in alongside Apple Health or Fitbit, so the picture is whole instead of split across apps that never compare notes.
Give Claude your real Oura history.
Sync Oura to Wellness Project over OAuth, add the MCP server to Claude, and ask about your actual readiness and HRV trends. Free during early access.
