Skip to main content
Glama
royreznik

Oura Ring MCP Server

by royreznik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Oura Ring MCP Server

  • whoop-mcp

    oryanomer1
    A
    license
    A
    quality
    A
    maintenance
    Ask Claude, Cursor, VS Code or any MCP client about your WHOOP recovery, HRV, sleep, strain and workouts, without giving it any way to change your data.
    10
    MIT

Related Servers

  • oura-mcp

    HalmSascha
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP clients to access Oura Ring health data such as sleep, readiness, activity, workouts, HRV, and event-centered recovery timelines using OAuth2 authentication.
    MIT

  • oura-ring-python-mcp

    osjayaprakash
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides read-only access to Oura Ring health and activity data, including sleep, readiness, activity, stress, SpO2, resilience, workouts, sessions, and heart rate via the Oura API v2.
    MIT

  • Polar MCP

    SuperShinyEyes
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables users to query Polar health data (activity, sleep, recovery, training sessions, heart rate) through MCP with secure authentication, redacted personal info, and bounded responses.
    -

  • Oura MCP Server

    robcerda
    A
    license
    A
    quality
    C
    maintenance
    Provides read-only access to Oura Ring data, including sleep, readiness, activity, heart rate, stress, workouts, and more, through MCP clients like Claude Desktop and Claude Code.
    22
    MIT

  • mcp-oura

    lyzetam
    A
    license
    Not graded
    quality
    B
    maintenance
    Gives Claude and other MCP clients read-only access to Oura Ring data through the Oura API v2, exposing sleep sessions, readiness, activity, stress, heart rate, workouts and long-range trends as queryable tools. It runs locally, evens out the API's quirks, and keeps credentials on the user's machine.
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.7/5.0

Scored across 14 tools

Disambiguation4/5

Tools mostly target distinct resources, and the descriptions actively route the agent (get_daily_overview for one day, get_trends for multi-day, list_* for one data type over a range). There is real overlap between get_daily_overview and the various list_* tools, and between list_daily_sleep and list_sleep_periods, but the descriptions explicitly delineate them, so misselection is unlikely.

Naming Consistency5/5

A clean, predictable verb_noun pattern holds throughout: get_profile, get_daily_overview, get_sleep_period, get_heart_rate, get_trends and list_daily_readiness, list_daily_sleep, list_sessions, list_sleep_periods, list_daily_activity, list_workouts, list_daily_health, list_tags, list_rest_mode_periods. The get_/list_ distinction usefully encodes single-vs-collection semantics.

Tool Count5/5

14 tools is well within the ideal band for a rich health-data domain, and each tool earns its place by covering a distinct Oura data type or aggregation level. No redundant or filler tools.

Completeness5/5

The surface covers profile/hardware, single-day overview, trends, readiness, sleep scores, individual sleep periods with hypnogram, activity, workouts, health metrics, tags, rest mode, and a raw heart-rate time series. Since the Oura API is read-only, the absence of write operations is appropriate, leaving no obvious gaps.

Maintenance

ActivityNo data
ResponsivenessNo issues

Resources