oura-mcp-unofficial

v0.4.1

Published

5 days ago

Unofficial local-first Oura MCP server for AI health, sleep and activity agents.

0High
0Medium
0Low

mcp model-context-protocol oura health sleep heart-rate fitness ai-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.

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    # 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 sleep 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.

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 |

Tools

Start with these:

oura_connection_status — verify local setup before calling Oura
oura_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 today
oura_weekly_summary — scorecard, comparison vs prior week, next-week plan

Auth & diagnostics

oura_capabilities, oura_agent_manifest, oura_privacy_audit, oura_cache_status
oura_get_auth_url, oura_exchange_code, oura_revoke_access

Profile

oura_get_personal_info

Daily 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_spo2

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-in
oura_weekly_review — review trends across activity, sleep and heart context
oura_heart_context_investigation — investigate heart-rate records (privacy-aware)

Resources

oura://capabilities, oura://agent-manifest
oura://personal-info
oura://latest/readiness
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.
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

# Optional
OURA_SCOPES="daily heartrate personal sleep 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

Hermes / remote setup

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.

Requirements

Node.js 20+
An Oura app at https://cloud.ouraring.com/oauth/applications with redirect URI http://127.0.0.1:3000/callback

Development

git clone https://github.com/davidmosiah/ouramcp.git
cd ouramcp
npm install
npm test
npm run build

Test with MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

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.