oura-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OURA_API_KEY | Yes | Your Oura API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oura_sleepC | Get daily sleep data including sleep score, sleep stages (REM, deep, light), and sleep duration |
| oura_readinessB | Get daily readiness score, HRV balance, resting heart rate, and body temperature |
| oura_activityB | Get daily activity data including steps, calories, and activity score |
| oura_heartrateC | Get heart rate data over time |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct Oura data domain (sleep, readiness, activity, heart rate), so an agent can generally tell them apart. There is slight potential overlap because readiness includes resting heart rate and HRV, while heartrate returns heart rate over time, but the descriptions make the intended distinction clear enough.
All four tools follow the same predictable oura_<noun> pattern (oura_sleep, oura_readiness, oura_activity, oura_heartrate). There are no mixed conventions, camelCase, or inconsistent verbs.
Four tools is a reasonable, focused set for a read-only Oura data server covering the main daily metrics. It is slightly thin compared to the full breadth of Oura data types, but not problematic.
The core daily metrics (sleep, readiness, activity, heart rate) are covered, but obvious Oura data surface areas are missing, such as workouts, tags, sessions, and SpO2. The server is read-only, which is acceptable for Oura's API, but the absence of a workout or tag endpoint is a notable gap.