Oura MCP server
Related Servers
Alternatives to Oura MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to access and query Oura Ring health data including sleep, activity, readiness, heart rate, and more via the Oura API.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.8MIT
- AlicenseAqualityAmaintenanceProvides 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.8MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates Oura Ring health data with Claude Desktop, providing resources, tools, and advanced analytics for sleep, activity, readiness, and health trends.1-
- 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
- AlicenseAqualityBmaintenanceEnables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.610MIT
TDQS
Scored across 18 tools
Each tool targets a unique Oura data domain (sleep, stress, ring, readiness, etc.) with clear, specific descriptions. The daily_summary tool is explicitly positioned as an overview and directs to more specific tools, avoiding overlap. No two tools appear to serve the same purpose.
All tools follow the identical 'oura_' prefix followed by a descriptive snake_case noun or phrase (e.g., oura_sleep_time, oura_heart_rate). The pattern is consistent and predictable, making it easy for an agent to infer the tool's function.
At 18 tools, the set is slightly above the typical 3-15 sweet spot, but it remains well-scoped because each tool corresponds to a distinct Oura data API endpoint. The count reflects the breadth of health metrics Oura tracks, and every tool earns its place without redundancy.
The tool set covers all major Oura data categories: sleep, readiness, activity, stress, resilience, heart rate, SpO2, workouts, meditation sessions, tags, rest mode, personal info, ring info, and analytical summaries. There are no obvious gaps in the lifecycle or data access needs, and the daily_summary provides a convenient aggregation.