Skip to main content
Glama
rollecode

Oura MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Oura MCP server

No user-submitted related servers found.

    Related Servers

    • 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

    • oura-mcp-server

      tommymulder
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop and Claude Code to access your personal Oura Ring health data—including sleep, readiness, activity, heart rate, and workouts—through local MCP tools.
      3 npm
      MIT

    • Oura MCP Server

      echocharlie
      A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to Oura ring biometrics via the Oura API, enabling Claude to query daily summaries, sleep, readiness, stress, workouts, baselines, and heart rate data. Designed to complement a Strava connector for joint analysis of training and recovery.
      8
      MIT

    • Oura Ring MCP Server

      ihadanidea
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to access and query personal Oura Ring health data, including activity, readiness, sleep, workouts, heart rate, stress, SpO2, sessions, and tags, via a self-hosted MCP server.
      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

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    Each tool maps to a distinct Oura data type (sleep, readiness, activity, stress, HR, workouts, etc.), so boundaries are mostly clear. The main overlap is oura_daily_summary, which bundles sleep/readiness/activity that individual tools also expose, but its description explicitly tells agents to use the specific tools for detail.

    Naming Consistency4/5

    All domain tools follow a clean oura_<noun> snake_case pattern, which is highly predictable. The lone exception is get_result_page, which lacks the oura_ prefix, but it is a generic pagination helper rather than a domain endpoint.

    Tool Count4/5

    19 tools is on the heavier side but each corresponds to a genuinely distinct Oura metric or resource, so they each earn their place. The set is neither bloated with redundant tools nor thin for the breadth of the Oura API.

    Completeness4/5

    The surface covers the full range of Oura read endpoints (sleep, readiness, resilience, activity, stress, HR, SpO2, VO2 max, cardiovascular age, tags, sessions, ring, profile, trends) plus paging. It is read-oriented, so write operations like logging tags or workouts are absent, but that matches the API's largely read-only nature.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources