Skip to main content
Glama
trenerok

oura-mcp-server

by trenerok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to oura-mcp-server

No user-submitted related servers found.

    Related Servers

    • Oura Ring MCP Server

      abekek
      A
      license
      Not graded
      quality
      D
      maintenance
      A Python-based Model Context Protocol server that provides AI assistants with access to Oura Ring health and fitness data across 15+ endpoints. It enables querying metrics like sleep, activity, readiness, and cardiovascular health through simple authentication and date-range filtering.
      MIT

    • Oura Ring MCP Server

      JamesLouie
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides access to Oura Ring health and fitness data through the Oura API v2, enabling retrieval of sleep, activity, readiness, and other health metrics.
      54 npm
      2
      MIT

    • oura-mcp

      johnie
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to access Oura Ring health data including activity, sleep, heart rate, stress, and personal info.
      15 npm
      2
      -

    • 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.
      1,020 npm
      MIT

    • Oura MCP

      davidmosiah
      A
      license
      B
      quality
      A
      maintenance
      Local-first MCP server that connects AI agents to your Oura Ring readiness, sleep, activity, and HRV data. Tokens never leave your machine.
      27
      396 npm
      4
      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.1/5.0

    Scored across 40 tools

    Disambiguation4/5

    Tools are mostly distinct: each data type typically has a list and a by_id variant, and descriptions clarify the difference. However, some pairs like get_sleep vs get_daily_sleep or get_tags vs get_enhanced_tags require careful reading, which could cause occasional misselection.

    Naming Consistency4/5

    Consistent snake_case with a get_ / get_..._by_id pattern for most data tools, and list_/get_/create_/update_/delete_ for webhooks. Minor inconsistency: list operations sometimes use singular nouns (get_sleep) and sometimes plural (get_workouts), and get_rest_mode_periods pairs with a singular by_id tool.

    Tool Count2/5

    40 tools is heavy for the apparent scope; many are thin list/by_id pairs that could be merged or parameterized. While each maps to an API endpoint, the count feels excessive and increases cognitive load.

    Completeness5/5

    Covers the full Oura v2 API surface: personal info, all health metrics with list and by_id, workouts, sessions, tags, enhanced tags, ring config, and full webhook CRUD plus renew. No obvious missing endpoints for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources