oura-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OURA_TOKEN | Yes | Your Oura Personal Access Token |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oura-fetchC | Fetch data from Oura Ring API endpoints |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Get readiness data | Retrieve readiness scores from your Oura ring |
| Get sleep data | Retrieve sleep metrics from your Oura ring |
| Get activity data | Retrieve activity metrics from your Oura ring |
| Get heart rate data | Retrieve heart rate data from your Oura ring |
| Get heart rate during sleep | Retrieve heart rate data during sleep periods |
| Get stress data | Retrieve stress metrics from your Oura ring |
| Get Oura tags | Retrieve tags from your Oura ring |
| Analyze health factors | Analyze how different factors affect your health metrics |
| Analyze meal effects on health | Analyze how different meals affect your health metrics |
| Verify calculations | Double-check calculations for accuracy |
| Get detailed sleep information | Retrieve and explain detailed sleep metrics from your Oura ring |
| Data handling guidelines | Guidelines for handling Oura data correctly |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The purpose is clear.
The single tool name 'oura-fetch' follows a clear verb_noun pattern, consistent with itself.
A single generic fetch tool is far too few for the broad Oura Ring API domain, which has many endpoints for different data types.
The tool surface is severely incomplete: it provides only a raw fetch without specific operations for sleep, activity, readiness, etc., leaving agents without necessary capabilities.