Oura MCP
Give your AI agent your Oura readiness, sleep, activity and HRV β without copy-pasting from the Oura app.
Local-first MCP server β tokens never leave your machine.
β‘ One-command install with Delx Wellness for Hermes:
npx -y delx-wellness-hermes setup β preconfigures this connector and the other 8 in a dedicated Hermes profile.
Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop β see the install section below.
HTTP (v2 stateless)
Default is stdio. Optional Streamable HTTP β no session id, JSON responses, loopback only:
npx -y oura-mcp-unofficial --http
Env: OURA_MCP_HOST, OURA_MCP_PORT, OURA_MCP_TRANSPORT=http.
Local-first MCP server that connects AI agents to your Oura Ring readiness, sleep, activity and HRV data.
Unofficial project. Not affiliated with, endorsed by or supported by Εura Health Oy. Oura is a trademark of its respective owner. Use this only with your own Oura account and in line with the Oura Cloud API terms.
Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about readiness, sleep and recovery β without copy-pasting numbers from the Oura app.
Part of Delx Wellness, a registry of local-first wellness MCP connectors.
If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.
Why this exists
Oura Ring produces some of the most refined personal health signals β readiness scores, sleep stages, HRV, daily activity, SpO2, body temperature trends. But it lives behind an OAuth API with per-scope authorization, and the data is split across multiple endpoints (daily readiness vs. detailed sleep periods vs. heart-rate streams).
This package handles the OAuth dance locally, normalizes responses across endpoints, and exposes Oura through the Model Context Protocol. Tokens never leave your machine. Privacy-mode defaults keep raw payloads opt-in.
Setup in 60 seconds
You'll need an Oura app (create one here) with redirect URI http://127.0.0.1:3000/callback.
npx -y oura-mcp-unofficial setup
npx -y oura-mcp-unofficial auth
npx -y oura-mcp-unofficial doctor
Recommended scopes:
daily heartrate personal workout spo2
Then add this to your MCP client config:
{
"mcpServers": {
"oura": {
"command": "npx",
"args": ["-y", "oura-mcp-unofficial"]
}
}
}
For Claude Desktop, run setup --client claude and the snippet is written for you.
Quickstart: see the data before you connect
No Oura account yet? Call oura_demo to get realistic example payloads for the
readiness, sleep and daily-summary tools, so your agent learns the data contract
before any OAuth setup. All values are synthetic and tagged is_demo: true.
Call oura_demo and show me what the readiness and sleep data looks like.
Real output from oura_demo (response_format=json, dates are relative to today):
{
"ok": true,
"is_demo": true,
"sample": {
"oura_daily_summary": {
"date": "2026-05-29",
"readiness": { "score": 78, "temperature_deviation": -0.1, "hrv_balance": 84 },
"sleep": { "score": 82, "efficiency": 89, "duration_min": 451, "deep_min": 92, "rem_min": 108 },
"activity": { "score": 86, "steps": 9420, "active_calories": 412, "target_calories": 500 },
"spo2": { "average": 96.8 }
},
"oura_wellness_context": {
"window": "last_24h",
"readiness_score": 78,
"readiness_band": "good",
"sleep_score": 82,
"sleep_efficiency": 89,
"hrv_balance": 84,
"recommendation": "Solid readiness and efficient sleep β green light for moderate-to-high intensity. A protein-forward breakfast keeps HRV trending up."
},
"oura_list_daily_readiness": {
"count": 3,
"records": [
{ "day": "2026-05-29", "score": 78, "contributors": { "hrv_balance": 84, "resting_heart_rate": 71, "sleep_balance": 76 } },
{ "day": "2026-05-28", "score": 74, "contributors": { "hrv_balance": 79, "resting_heart_rate": 73, "sleep_balance": 72 } },
{ "day": "2026-05-27", "score": 69, "contributors": { "hrv_balance": 68, "resting_heart_rate": 80, "sleep_balance": 65 } }
]
}
},
"notes": [
"All sample data is synthetic; tagged with is_demo=true.",
"Real calls return live data from the Oura Cloud v2 API after OAuth setup."
]
}
When you're ready to connect your own ring, call oura_quickstart for a
personalized 3-step setup walkthrough, then follow Setup in 60 seconds.
Try it with your agent
Three things to ask first:
Use oura_connection_status to check setup, then run oura_daily_summary.
Give me a 5-line operating brief for today.
Call oura_weekly_summary with response_format=json. Identify my biggest
readiness/sleep bottleneck and give me a next-week plan.
Use the oura_daily_checkin prompt, focus=sleep.
Don't claim Oura can prove anything it can't.
Data availability
This package uses the official Oura Cloud API v2. When this README says raw, it means the upstream Oura JSON for a supported endpoint β not raw device sensor streams.
| Data | Available | Notes |
|---|
| Daily readiness score + contributors | β | Requires daily scope |
| Daily sleep score + sleep periods | β | Requires daily and/or sleep scope |
| Sleep stages + timing | β | When Oura returns scored sleep |
| Daily activity (steps, calories, MET) | β | Requires daily scope |
| Heart-rate time series | β | When ring/membership/scope expose it |
| HRV (overnight, via daily summaries) | β | Surfaced through readiness contributors |
| SpO2 (daily averages during sleep) | β | Requires spo2 scope; supported devices |
| Workouts + sessions + tags | β | Requires workout/session/tag scopes |
| Personal info (DOB, sex, height, weight) | β | Requires personal scope |
| Continuous sensor telemetry | β | Not exposed by Oura Cloud API |
Start with these:
oura_demo β realistic synthetic readiness/sleep/activity payloads (no account needed; see Quickstart)oura_quickstart β personalized 3-step setup walkthrough that adapts to your current stateoura_connection_status β verify local setup before calling Ouraoura_data_inventory β inventory supported data domains, scopes, privacy modes and recommended first calls without calling Oura APIs.oura_daily_summary β readiness, sleep, activity and SpO2 brief for todayoura_weekly_summary β scorecard, comparison vs prior week, next-week plan
Auth & diagnostics
oura_capabilities, oura_agent_manifest, oura_privacy_audit, oura_cache_statusoura_get_auth_url, oura_exchange_code, oura_revoke_access
Profile
Daily collections (cursor-paginated with next_token, after/before filters and privacy-mode override)
oura_list_daily_readiness, oura_list_daily_sleep, oura_list_daily_activity, oura_list_daily_spo2- Offset ISO inputs keep their written calendar date when mapped to Oura's date-only
start_date and end_date parameters; invalid dates fail before a network request.
- Oura v2 has no integer page index. Resume with
next_token from the previous response; if truncated is true, raise limit or set all_pages. See docs/pagination.md.
Detailed collections
oura_list_sleep, oura_list_workouts, oura_list_heartrate, oura_list_sessions, oura_list_tags
Prompts
oura_daily_checkin β practical daily health and readiness check-inoura_weekly_review β review trends across activity, sleep and heart contextoura_heart_context_investigation β investigate heart-rate records (privacy-aware)
Resources
oura://capabilities, oura://agent-manifestoura://personal-infooura://latest/readiness β the single newest readiness record. Use this for "my latest readiness": Oura serves collections oldest-first with no sort parameter, so oura_list_daily_readiness with limit: 1 returns the oldest record in the window, not the newest.oura://summary/daily, oura://summary/weekly
Privacy & security
- OAuth tokens are stored in
~/.oura-mcp/tokens.json with 0600 permissions and are never returned by tools.
- The server never prints access or refresh tokens.
OURA_PRIVACY_MODE defaults to structured. Raw Oura JSON is opt-in via raw mode or per-call override.- Structured mode preserves upstream physiological fields, including fields added by Oura later, while removing GPS and secret-bearing values.
- Personal info (DOB, sex, height, weight) is only accessible when the user grants the
personal scope.
- The MCP client never sees access or refresh tokens.
- This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or treatment.
Configuration
setup writes most of these into ~/.oura-mcp/config.json (0600). Manual env override is supported:
OURA_CLIENT_ID=β¦
OURA_CLIENT_SECRET=β¦
OURA_REDIRECT_URI=http://127.0.0.1:3000/callback
OURA_SCOPES="daily heartrate personal workout spo2"
OURA_PRIVACY_MODE=structured
OURA_CACHE=sqlite
OURA_TOKEN_PATH=~/.oura-mcp/tokens.json
OURA_CACHE_PATH=~/.oura-mcp/cache.sqlite
Hermes / remote setup
npx -y oura-mcp-unofficial setup --client hermes --no-auth
npx -y oura-mcp-unofficial auth
npx -y oura-mcp-unofficial doctor --client hermes
hermes mcp test oura
After Hermes config changes, use /reload-mcp or hermes mcp test oura. Don't restart the gateway for normal data access.
If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.oura-mcp/tokens.json to the server with chmod 600.
Requirements
Development
git clone https://github.com/davidmosiah/oura-mcp.git
cd oura-mcp
npm install
npm test
npm run build
Test with MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
Links
See also
The full Delx Wellness connector library:
One-command setup for Hermes β preconfigures every connector above plus wellness skills + onboarding: delx-wellness-hermes.
License
MIT β see LICENSE.
Disclaimer
This software is provided as-is. It is not a medical device, does not provide medical advice, and should not be used for diagnosis or treatment. Always consult qualified professionals for medical concerns.
Skill or MCP
Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:
npx -y oura-mcp-unofficial call oura_connection_status --json '{}'
Copy skill/SKILL.md into your agent skills dir.
