Oura MCP Server
Related Servers
Alternatives to Oura MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides 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.3,386 npmMIT
- AlicenseBqualityDmaintenanceEnables users to query their Oura Ring data (sleep, readiness, activity, heart rate) via natural language through any MCP-compatible LLM.410 npm1MIT
- AlicenseAqualityCmaintenanceProvides 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.22MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceGives 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
- AlicenseNot gradedqualityDmaintenanceEnables 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.6 npmMIT
TDQS
Scored across 6 tools
The tools have clear distinctions between readiness, resilience, and sleep data types, but there is significant overlap between the 'get_X_data' and 'get_today_X_data' pairs. An agent might confuse which tool to use for today's data versus a date range, though the descriptions clarify the difference.
All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (e.g., 'get_readiness_data', 'get_today_sleep_data'). The naming is predictable and uniform across all six tools.
Six tools are reasonable for a health/fitness data server, covering three data types with both date-range and today-specific variants. It's slightly over-scoped as the 'today' tools could be handled by the date-range tools with default parameters, but it's still well within an appropriate range.
The server provides read-only access to readiness, resilience, and sleep data, which aligns with Oura's typical API capabilities. However, there are notable gaps: no tools for writing or updating data (e.g., setting goals or annotations), and no coverage of other Oura metrics like activity or heart rate, limiting the surface for comprehensive health tracking.