oura-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OURA_PAT | No | Your Oura Personal Access Token | |
| OURA_PAT_FILE | No | Path to a file containing your Oura Personal Access Token (mode 600 recommended) |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oura_collectionsA | The 19 Oura collections, what each one carries and which parameters it takes. Use it before |
| oura_queryA | Fetches a COMPLETE Oura collection over the requested range. Follows pagination to the end: Oura returns The range is INCLUSIVE on both ends: equal Date-range collections use YYYY-MM-DD. |
| oura_todayA | Last night's sleep and today's readiness, with the days before them. ONE CALL INSTEAD OF FOUR, and that is the whole of it. «How did I sleep?»
is the most common question there is, and answering it well means today's
two records plus enough history to know whether they are unusual — which
was four round trips through IT COMPUTES NOTHING. No average, no delta, no «your HRV is up 12%». The records come back raw and the comparison happens where the method can be cited. That is not an omission: across nine years of real data, three out of four changes between consecutive measurements fall inside the metric's own normal swing, so a server that hands over a percentage without saying how much the metric wanders on its own is manufacturing a signal.
|
| oura_checkA | Self-check: is there a credential, and does Oura respond? Exposing nothing. Returns neither the token nor any health value. It reports the token's LENGTH, never the token: diagnostic messages are the ones most often copied into chats and issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Oura collection catalog | The 19 collections, what each carries and which parameters it takes. Static: no network, no credentials, no health data. |
TDQS
Scored across 4 tools
Each tool has a distinct role: oura_today is a composite sleep/readiness shortcut, oura_query is the general-purpose collection fetcher, oura_collections is discovery, and oura_check is diagnostics. oura_today partially overlaps with oura_query (which can also fetch sleep/readiness), but the descriptions clearly frame today as a convenience wrapper, so misselection risk is low.
All four tools share a uniform oura_ prefix followed by a single lowercase snake_case word (today, check, collections, query). The convention is applied without deviation, making the set easy to scan and predict.
Four tools is on the lean side but each earns its place: a diagnostic, a discovery catalog, a general query, and a composite shortcut. A generic query tool absorbs most remaining coverage, so nothing feels padded or redundant.
The surface covers the read-only Oura domain well: catalog discovery (oura_collections), generic full-pagination retrieval across all collections (oura_query), a common composite case (oura_today), and credential/connectivity validation (oura_check). No obvious read-path gaps remain for the stated purpose.