Natural-language access to your Oura data through Claude. Local SQLite mirror, natural-language annotations, and MCP tools for actually asking questions about your health data.

Oura already tracks sleep, readiness, activity, heart rate, stress, and tags.

But the interesting questions are usually more personal:

• "Does alcohol actually affect my readiness?"
• "Do late coffees hurt my deep sleep?"
• "Why has my energy been low lately?"
• "How long do I take to recover after travel or hard workouts?"
• "What changed on the nights where I slept really well?"

oura-ring-mcp lets Claude analyze your Oura data locally through MCP, with your own annotations and context stored in SQLite.

You can log things naturally:

• "I had 2 beers Thursday from 7pm to midnight. Log it."
• "I was sick from Monday to Wednesday."
• "Late coffee today at 4pm."

And then actually ask questions about the patterns behind your health data.

Everything is local-first. After sync, most queries run against your local SQLite mirror instead of repeatedly hitting the Oura API.

Sensitive data warning: this project works with personal health data. Tokens and synced data are stored locally at ~/.config/oura-ring-mcp/ with 0600 permissions and are never sent anywhere by this software except to api.ouraring.com for Oura API requests. Your MCP client may see whatever data you ask it to analyze.

Why I Built This

I wanted something more useful than another dashboard.

The raw metrics from Oura are already good. The missing piece is context: coffee, alcohol, illness, travel, late meals, stressful weeks, bad sleep hygiene, or whatever else was actually happening in life.

This project gives an LLM memory for the things Oura does not capture. The result feels much closer to talking to a health journal than scrolling through charts.

What It Does

• Syncs your Oura data into a local SQLite database.
• Exposes your data through MCP tools for Claude Code and other MCP clients.
• Lets you store natural-language annotations locally.
• Makes it easy to analyze trends, recovery, sleep, stress, workouts, and habits over time.
• Keeps everything local-first and your MCP client may see whatever data you ask it to analyze..

Currently supports:

• sleep
• readiness
• activity
• heart rate
• stress
• resilience
• SpO2
• VO2 max
• cardiovascular age
• sleep periods
• workouts
• sessions
• rest mode periods
• enhanced tags
• local annotations

Example Prompts

Sleep and recovery

• "Show me my last 14 days of sleep, readiness, and activity."
• "Which night this month had the worst sleep, and what changed?"
• "How long did it take my resting heart rate to recover after my last alcohol day?"
• "Walk me through last night's sleep periods and heart-rate pattern."

Trends and comparisons

• "Compare this week's sleep to the previous week."
• "Show my readiness rolling average over the last 60 days."
• "Compare weekdays vs weekends for sleep score and bedtime."
• "What is my VO2 max trajectory?"

Logging context

• "I had 2 beers Thursday from 7pm to midnight. Log it."
• "I was sick from Monday to Wednesday. Log a cold annotation."
• "I had a late coffee today at 4pm. Log it."
• "List all my alcohol annotations from the last 3 months."

The fun part

• "Across my alcohol annotations, what usually happens to next-day readiness?"
• "Is there a relationship between caffeine days and deep sleep?"
• "Do hard workout days change my sleep or recovery?"
• "My energy has been low lately. What patterns should I look at?"

Quick Start

You need Node.js 20+ and an Oura account.

1. Register an Oura OAuth App

Go to https://cloud.ouraring.com/oauth/applications and create a new app.

• Redirect URI: http://127.0.0.1:8765/callback
• Privacy Policy URL: https://github.com/FelixWag/oura-ring-mcp/blob/main/PRIVACY.md
• Terms of Service URL: https://github.com/FelixWag/oura-ring-mcp/blob/main/TERMS.md

Copy the Client ID and Client Secret.

2. Clone, Install, Build

git clone https://github.com/FelixWag/oura-ring-mcp.git
cd oura-ring-mcp
npm install
npm run build

3. Configure, Authorize, Sync

npm run init

That one command:

1. writes your local .env,
2. opens the Oura OAuth login,
3. stores tokens locally,
4. syncs your recent Oura history into SQLite.

Want more history?

npm run sync -- --since 240

Connect Claude Code

claude mcp add oura node "$(pwd)/dist/index.js"

Restart Claude Code, run /mcp, and check that oura is listed.

Then try:

Show me my last 7 days of Oura summaries with annotations.

Why Local-First Matters

This project stores your synced data and annotations locally in SQLite instead of forwarding everything through another cloud service.

After sync, most reads happen locally:

• faster queries,
• less API usage,
• offline-friendly access,
• easier experimentation,
• and more privacy.

The Oura API is read-only for user data. Local annotations intentionally stay local.

Development

npm run dev
npm test
npm run typecheck
npm run build

The stack is intentionally simple:

• TypeScript
• Node.js
• SQLite
• MCP SDK
• zod
• Vitest

Security

• Tokens and SQLite files use 0600 permissions.
• .env and local databases are ignored by git.
• SQL uses prepared statements.
• No shell execution or arbitrary filesystem access.
• The Oura API remains read-only.
• This is not medical advice or a medical device.

Raw Access

Derived Metrics

Tags And Annotations

Local annotations mirror Oura's EnhancedTagModel fields: tag_type_code, custom_name, start_time, end_time, start_day, end_day, and comment, plus source and oura_id for provenance.

Because the public Oura API is read-only for user data, annotation writes are local only. This is intentional: it gives the LLM memory for things Oura does not capture without pretending to write back to Oura.

Local Mirror

Read preference for local-first tools:

• auto (default): use local data when available; fetch missing/recent data from Oura and upsert it locally.
• local: offline mode; only return what is already in SQLite.
• api: force a fresh Oura API read and upsert the result locally.

Configuration

.env is loaded from the project root, even when an MCP host starts the binary from another working directory.

Troubleshooting

No saved tokens at ...
Run npm run oauth-login.

invalid_client during OAuth
Check that OURA_CLIENT_ID and OURA_CLIENT_SECRET in .env match the Oura application you created.

Address already in use :::8765
Change the port in OURA_REDIRECT_URI, update the same redirect URI in Oura's application settings, then run npm run oauth-login again.

Scope-related 401 during sync
Run npm run oauth-login again so Oura grants the latest scope set.

License

MIT