Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Ouramcp

by davidmosiahversion 0.4.6i★ –iRuns on your computer
Registry nameio.github.davidmosiah/ouramcp

Install

Overview

Description from the maker (original English)

Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Clinics & health
  • You need to fill in: OURA_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: OURA_CLIENT_ID, OURA_CLIENT_SECRET, OURA_REDIRECT_URI, OURA_TOKEN_PATH, OURA_PRIVACY_MODE, OURA_CACHE, OURA_CACHE_PATH, OURA_NO_CACHE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ouramcp": {
      "command": "npx",
      "args": [
        "-y",
        "oura-mcp-unofficial"
      ],
      "env": {
        "OURA_CLIENT_ID": "your-value",
        "OURA_CLIENT_SECRET": "your-value",
        "OURA_REDIRECT_URI": "your-value",
        "OURA_TOKEN_PATH": "your-value",
        "OURA_PRIVACY_MODE": "your-value",
        "OURA_CACHE": "your-value",
        "OURA_CACHE_PATH": "your-value",
        "OURA_NO_CACHE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ouramcp --env OURA_CLIENT_ID=your-value --env OURA_CLIENT_SECRET=your-value --env OURA_REDIRECT_URI=your-value --env OURA_TOKEN_PATH=your-value --env OURA_PRIVACY_MODE=your-value --env OURA_CACHE=your-value --env OURA_CACHE_PATH=your-value --env OURA_NO_CACHE=your-value -- npx -y oura-mcp-unofficial

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ouramcp": {
      "command": "npx",
      "args": [
        "-y",
        "oura-mcp-unofficial"
      ],
      "env": {
        "OURA_CLIENT_ID": "your-value",
        "OURA_CLIENT_SECRET": "your-value",
        "OURA_REDIRECT_URI": "your-value",
        "OURA_TOKEN_PATH": "your-value",
        "OURA_PRIVACY_MODE": "your-value",
        "OURA_CACHE": "your-value",
        "OURA_CACHE_PATH": "your-value",
        "OURA_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ouramcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "oura-mcp-unofficial"
      ],
      "env": {
        "OURA_CLIENT_ID": "your-value",
        "OURA_CLIENT_SECRET": "your-value",
        "OURA_REDIRECT_URI": "your-value",
        "OURA_TOKEN_PATH": "your-value",
        "OURA_PRIVACY_MODE": "your-value",
        "OURA_CACHE": "your-value",
        "OURA_CACHE_PATH": "your-value",
        "OURA_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • OURA_CLIENT_ID env
    Oura OAuth client ID. Optional when configured with oura-mcp-server setup.
  • OURA_CLIENT_SECRET secret env
    Oura OAuth client secret. Prefer oura-mcp-server setup so this secret is stored in ~/.oura-mcp/config.json instead of MCP client config.
  • OURA_REDIRECT_URI env
    Redirect URI configured in the Oura Developer Dashboard. Optional when configured with oura-mcp-server setup.
  • OURA_TOKEN_PATH env
    Optional local path for OAuth tokens. Defaults to ~/.oura-mcp/tokens.json.
  • OURA_PRIVACY_MODE env
    Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Oura API payloads, not continuous 24/7 raw sensor telemetry.
  • OURA_CACHE env
    Optional SQLite cache toggle. Set to true or sqlite to enable.
  • OURA_CACHE_PATH env
    Optional local SQLite cache path. Defaults to ~/.oura-mcp/cache.sqlite.
  • OURA_NO_CACHE env
    Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account davidmosiah, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

  • More stars than 0% of the other 1022 servers in this category
  • Published to the registry more recently than 12% of the other 1022 servers in this category
  • Basic checks equal to or better than 100% of the other 1022 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ouramcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: OURA_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.6) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Langcare MCP FHIR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated today
Install

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago
Install

An MCP FHIR server written in Go for EMR systems like Epic and Cerner

Runs on your computer★ 70MITUpdated 9 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Upgrading to 0.8.0: read the migration guide for local-only HTTP, disabled authenticated-response caching, and stricter input/profile limits.

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

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

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

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.

DataAvailableNotes
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_demo — realistic synthetic readiness/sleep/activity payloads (no account needed; see Quickstart)
  • oura_quickstart — personalized 3-step setup walkthrough that adapts to your current state
  • 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 (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-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 — 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

Optional

OURA_SCOPES="daily heartrate personal workout spo2" OURA_PRIVACY_MODE=structured # summary | structured | raw OURA_CACHE=sqlite # no effect: authenticated responses are never cached OURA_TOKEN_

Only the beginning is shown; read the rest in the repo

Ask PopNx