Skip to main content
Glama
louis030195

oura-mcp

by louis030195
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to oura-mcp

No user-submitted related servers found.

    Related Servers

    • Oura MCP Server

      koji117
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Oura Ring health data, including sleep, activity, readiness, and stress metrics via the Model Context Protocol. It enables users to query their personal biometric information and daily health summaries through natural language in MCP-compatible clients.
      681 npm
      MIT

    • Oura MCP Server

      tomekkorbak
      A
      license
      B
      quality
      F
      maintenance
      Enables querying sleep, readiness, and resilience data from the Oura API via the Model Context Protocol (MCP), allowing natural language interaction and seamless integration with tools like Claude.
      6
      39
      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

    B3.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct Oura data domain (sleep, readiness, activity, heart rate), so an agent can generally tell them apart. There is slight potential overlap because readiness includes resting heart rate and HRV, while heartrate returns heart rate over time, but the descriptions make the intended distinction clear enough.

    Naming Consistency5/5

    All four tools follow the same predictable oura_<noun> pattern (oura_sleep, oura_readiness, oura_activity, oura_heartrate). There are no mixed conventions, camelCase, or inconsistent verbs.

    Tool Count4/5

    Four tools is a reasonable, focused set for a read-only Oura data server covering the main daily metrics. It is slightly thin compared to the full breadth of Oura data types, but not problematic.

    Completeness3/5

    The core daily metrics (sleep, readiness, activity, heart rate) are covered, but obvious Oura data surface areas are missing, such as workouts, tags, sessions, and SpO2. The server is read-only, which is acceptable for Oura's API, but the absence of a workout or tag endpoint is a notable gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources