Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
OURA_CLIENT_ID, OURA_CLIENT_SECRET, OURA_REDIRECT_URI, OURA_TOKEN_PATH, OURA_PRIVACY_MODE, OURA_CACHE, OURA_CACHE_PATH, OURA_NO_CACHEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
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-unofficialFill in the empty values before running it.
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.
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.
OURA_CLIENT_ID envOURA_REDIRECT_URI envOURA_TOKEN_PATH envOURA_PRIVACY_MODE envOURA_CACHE envOURA_CACHE_PATH envOURA_NO_CACHE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account davidmosiah, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: OURA_CLIENT_SECRET
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).
The GitHub repo last changed –, and the latest version (0.4.6) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Mirobody, FHIR MCP Server, Langcare MCP FHIR
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
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
An MCP FHIR server written in Go for EMR systems like Epic and Cerner
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.
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.
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 (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_spo2start_date and end_date parameters; invalid dates fail before a network request.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_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
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