oura-mcp-unofficial
Advanced tools
Unofficial local-first Oura MCP server for AI health, sleep and activity agents.
⚡ 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.
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.
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.
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 # interactive: paste client id + secret
npx -y oura-mcp-unofficial auth # opens browser, captures the OAuth code
npx -y oura-mcp-unofficial doctor # verifies you're ready
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.
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.
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.
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 planAuth & diagnostics
oura_capabilities, oura_agent_manifest, oura_privacy_audit, oura_cache_statusoura_get_auth_url, oura_exchange_code, oura_revoke_accessProfile
oura_get_personal_infoDaily collections (paginated, with after/before filters and privacy-mode override)
oura_list_daily_readiness, oura_list_daily_sleep, oura_list_daily_activity, oura_list_daily_spo2start_date and end_date parameters; invalid dates fail before a network request.Detailed collections
oura_list_sleep, oura_list_workouts, oura_list_heartrate, oura_list_sessions, oura_list_tagsoura_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)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~/.oura-mcp/tokens.json with 0600 permissions and are never returned by tools.OURA_PRIVACY_MODE defaults to structured. Raw Oura JSON is opt-in via raw mode or per-call override.personal scope.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
# Optional
OURA_SCOPES="daily heartrate personal workout spo2"
OURA_PRIVACY_MODE=structured # summary | structured | raw
OURA_CACHE=sqlite # optional read-through cache
OURA_TOKEN_PATH=~/.oura-mcp/tokens.json
OURA_CACHE_PATH=~/.oura-mcp/cache.sqlite
npx -y oura-mcp-unofficial setup --client hermes --no-auth
npx -y oura-mcp-unofficial auth # run locally if browser auth is needed
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.
http://127.0.0.1:3000/callbackgit 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
The full Delx Wellness connector library:
| Provider | Package | Repo |
|---|---|---|
| WHOOP | whoop-mcp-unofficial | whoop-mcp |
| Oura | oura-mcp-unofficial | oura-mcp |
| Garmin | garmin-mcp-unofficial | garminmcp |
| Strava | strava-mcp-unofficial | strava-mcp |
| Fitbit | fitbit-mcp-unofficial | fitbitmcp |
| Withings | withings-mcp-unofficial | withingsmcp |
| Apple Health | apple-health-mcp-unofficial | apple-health-mcp |
| Polar | polar-mcp-unofficial | polarmcp |
| Nourish (nutrition) | wellness-nourish | wellness-nourish |
One-command setup for Hermes — preconfigures every connector above plus wellness skills + onboarding: delx-wellness-hermes.
MIT — see LICENSE.
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.
FAQs
Unofficial local-first Oura MCP server for AI health, sleep and activity agents.
The npm package oura-mcp-unofficial receives a total of 914 weekly downloads. As such, oura-mcp-unofficial popularity was classified as not popular.
We found that oura-mcp-unofficial demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.
Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.