Oura Ring MCP Server

Oura Ring MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Sleep, readiness, HRV, resting heart rate, activity and stress from your Oura Ring.

What you get

• Compact by default. — Tools return per-day values plus statistics with a
• One codebase, two transports. — stdio for local use, streamable-http
• Timezone-correct. — Oura filters some endpoints by an internal UTC
• Survives flaky networks. — Follows next_token pagination, retries
• Try before authorizing. — Oura's sandbox works with no credentials at all

What the assistant can call

Once Oura Ring is connected, these are the calls the assistant has available:

• get_daily_summary — Sleep, readiness and activity scores at once
• get_sleep — Sleep stages, efficiency, HRV, resting HR, breathing, temperature
• get_sleep_score — Daily sleep score only — lighter than get_sleep
• get_readiness — Readiness score, HRV balance, temperature deviation
• get_activity — Activity score, steps, calories
• get_heartrate — Per-minute heart rate collapsed to daily stats
• get_spo2 — Blood oxygen during sleep, breathing disturbance index
• get_stress — Time under load and in recovery
• get_heart_health — Cardiovascular age, VO₂max
• get_tags — Tags you entered in the Oura app
• get_status — Server mode and authorization state

Configuration and credentials

You will need 5 environment variables: OURA_MCP_TOKEN, OURA_CLIENT_ID, OURA_CLIENT_SECRET, OURA_PUBLIC_URL, YOUR_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Oura Ring's toolset — get_daily_summary, get_sleep, get_sleep_score and 8 more — is a fair guide to whether it matches your workflow. It is maintained by AntVsl; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Oura Ring.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the oura ring mcp server does with a few real requests.