Skip to main content
Glama
YasuakiOmokawa

oura-mcp

by YasuakiOmokawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to oura-mcp

No user-submitted related servers found.

    Related Servers

    • Oura MCP Server

      jaredstauffer
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables access to Oura Ring data, including sleep, activity, readiness, and other health metrics, through local stdio or remote HTTP with OAuth.
      10 npm
      -

    • oura-mcp

      proscar87
      A
      license
      A
      quality
      A
      maintenance
      Exposes the Oura API v2 as an MCP server with tools to query all 19 data collections (e.g., sleep, heartrate) with automatic pagination and explicit truncation warnings.
      4
      MIT

    • mcp-server-withings

      borgels
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Withings Health API with per-user OAuth2, enabling users to securely access their own health data (measures, activity, sleep, workouts, heart rate, devices, and goals) and optionally add measurements.
      12
      Apache 2.0

    • mcp-whoop

      PilarJ
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the WHOOP v2 API, enabling users to retrieve health data such as cycles, recovery, sleep, and workouts. It uses GitHub OAuth for authentication and is designed for remote use over HTTP.
      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/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing endpoints, generic GET requests, initiating OAuth, checking auth status, and clearing tokens. No overlap or ambiguity in their roles.

    Naming Consistency4/5

    All tools share the 'oura_' prefix, and most follow a verb_noun pattern (e.g., oura_authenticate, oura_auth_status). Minor inconsistency with 'oura_api_get' and 'oura_api_list_paths' mixing 'api' with the verb, but overall pattern is maintained.

    Tool Count5/5

    With only 5 tools, the server is well-scoped for its purpose: authentication management and a generic GET endpoint. No unnecessary tools.

    Completeness3/5

    The server covers authentication and read operations via a generic GET, but lacks write operations (POST/PUT/DELETE) or any specialized endpoints. This may be sufficient for some use cases but leaves gaps for a full API surface.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources