All connectors
Oura

oura-mcp-unofficial

Oura Ring MCP server for AI agents

The Oura connector for AI agents is a local MCP server that uses the official Oura Cloud API v2. It exposes user-authorized readiness, sleep, activity, HRV and SpO2 context while keeping OAuth tokens outside model responses.

ReadinessSleepActivityHRVSpO2Shared profile
A recovery space with mobility work and calm wellness analytics
OAuth 2.0

Best for sleep-first agents and coaches that need an Oura MCP connector for readiness, overnight recovery and daily activity context.

MCP server answers

The Oura connector for AI agents is a local MCP server provided by oura-mcp-unofficial. It uses the official Oura Cloud API v2 and user-authorized OAuth to expose readiness, sleep, activity, HRV and SpO2 context to an MCP-compatible client; OAuth tokens stay outside model responses and Delx does not host a copy of the data.

Compare this connector with the other wellness paths
What is the Oura Ring MCP server?

The Oura connector for AI agents is a local MCP server provided by oura-mcp-unofficial. It uses the official Oura Cloud API v2 and user-authorized OAuth to expose readiness, sleep, activity, HRV and SpO2 context to an MCP-compatible client; OAuth tokens stay outside model responses and Delx does not host a copy of the data.

How do I install Oura Ring MCP?

Run npx -y oura-mcp-unofficial setup, then npx -y oura-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.

What can an agent read from Oura Ring?

The available records start with Daily readiness score and contributors, Daily sleep score and sleep periods, Sleep stages and timing, Daily activity, steps, calories and MET. Check Data Availability for scope, device and export limitations before using any result.

Quick Start

terminal
npx -y oura-mcp-unofficial setup
npx -y oura-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "oura": {
      "command": "npx",
      "args": ["-y", "oura-mcp-unofficial"]
    }
  }
}
  1. 01

    Create an Oura OAuth app.

  2. 02

    Use redirect URI http://127.0.0.1:3000/callback.

  3. 03

    Request the scopes that match the data your agent needs.

Recommended scopes

daily heartrate personal sleep workout spo2

Data Availability

Available

Daily readiness score and contributors

Requires daily scope.

Available

Daily sleep score and sleep periods

Requires daily and/or sleep scope.

Available

Sleep stages and timing

Available when Oura returns scored sleep.

Available

Daily activity, steps, calories and MET

Requires daily scope.

Conditional

Heart-rate time series

Depends on ring, membership and granted scope.

Available

HRV and SpO2

HRV is surfaced through readiness; SpO2 requires spo2 scope and supported devices.

Not exposed

Continuous sensor telemetry

Not exposed by the Oura Cloud API.

Agent Tools

Profile and onboarding

  • oura_profile_get
  • oura_profile_update
  • oura_onboarding

Start here

  • oura_connection_status
  • oura_daily_summary
  • oura_weekly_summary

Auth and 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

  • 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 and Resources

Prompts

  • oura_daily_checkin
  • oura_weekly_review
  • oura_heart_context_investigation

Resources

  • oura://capabilities
  • oura://agent-manifest
  • oura://personal-info
  • oura://latest/readiness
  • oura://summary/daily
  • oura://summary/weekly

Privacy Model

OAuth tokens stay local.
The connector is scoped to the permissions the user grants.
Agent-facing summaries can avoid sensitive raw payloads.
Raw means upstream Oura API JSON, not raw ring sensor streams.
Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.