oura-mcp
Related Servers
Alternatives to oura-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for the Oura Ring API v2, providing access to sleep, activity, readiness, heart rate, and workout data via OAuth.5206 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for the Oura Ring API v2, enabling natural language queries about sleep, readiness, activity, heart rate, and more.201MIT
- AlicenseNot gradedqualityBmaintenanceAn 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.18 npmISC
- AlicenseAqualityCmaintenanceComprehensive MCP server for the Oura Ring API v2, exposing 17 tools to access sleep, activity, heart rate, stress, SpO2, workouts, and user data.171MIT
- 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 gradedqualityBmaintenanceEnables MCP clients to query Oura Ring health data, including sleep, readiness, HRV, activity, and SpO2, through OAuth2-authenticated tools running on Cloudflare Workers.18 npm1MIT
TDQS
Scored across 6 tools
Each tool serves a unique purpose: compare analyzes difference between periods, relate analyzes correlation between metrics, query fetches raw data, today bundles common data, collections provides metadata, and check verifies connectivity. There is no ambiguity between tools.
All tools share the 'oura_' prefix, making the domain clear. However, the verbs are not consistently verb_noun: 'collections' and 'today' are nouns, while 'compare', 'relate', 'check', and 'query' are verbs. Still, the pattern is predictable and easily recognizable.
Six tools is well within the ideal 3-15 range and covers the full scope of the server's purpose: data retrieval, metadata discovery, convenience access, and statistical analysis. No tool feels redundant or extraneous.
The tool surface fully addresses the Oura data domain: raw data access via query, metadata via collections, common use-case via today, and two analysis methods (compare and relate) plus a health check. No obvious gaps exist; the server is self-contained for its intended functionality.