oura-ring-mcp-server
Related Servers
Alternatives to oura-ring-mcp-server
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.593 npm1MIT
- FlicenseNot 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.14 npm-
- 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
- AlicenseBqualityDmaintenanceEnables users to query their Oura Ring data (sleep, readiness, activity, heart rate) via natural language through any MCP-compatible LLM.422 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to query Oura Ring health data (sleep, readiness, activity, heart rate, SpO2, stress) via a remote MCP server.15 npmMIT
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with structured, semantic access to your Oura Ring health data.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'info' returns server metadata, while 'oura_data' fetches Oura Ring API data. There is no overlap or ambiguity.
With only two tools, a consistent naming pattern is hard to establish. 'info' is a noun, while 'oura_data' uses underscore separation. The names are not chaotic but lack a strong, predictable pattern.
Having only two tools for a server that covers a wide range of health data (18+ collections) feels thin. The generic 'oura_data' tool consolidates all data retrieval, which is efficient but potentially overloaded.
The server covers read access to many Oura Ring data collections, but lacks any write operations (create, update, delete). For a comprehensive API surface, this is a notable gap.