Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents.
Ouramcp MCP server exists for a simple reason — assistants are far more useful when they can act on Ouramcp directly instead of describing what you should do. Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents.
Give your AI agent your Oura readiness, sleep, activity and HRV — without copy-pasting from the Oura app.
Once Ouramcp is connected, these are the calls the assistant has available:
oura_demo — realistic synthetic readiness/sleep/activity payloads (no account needed; see Quickstart)oura_quickstart — personalized 3-step setup walkthrough that adapts to your current stateoura_connection_status — verify local setup before calling Ouraoura_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Oura APIsoura_daily_summary — readiness, sleep, activity and SpO2 brief for todayoura_weekly_summary — scorecard, comparison vs prior week, next-week planYou will need 4 environment variables: OURA_CLIENT_ID, OURA_CLIENT_SECRET, OURA_TOKEN_PATH, OURA_CACHE_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
http://127.0.0.1:3000/callbackdelx-wellness-hermes on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ouramcp's toolset — oura_demo, oura_quickstart, oura_connection_status and 3 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| oura_demo | realistic synthetic readiness/sleep/activity payloads (no account needed; see [Quickstart](#quickstart-see-the-data-before-you-connect)) |
| oura_quickstart | personalized 3-step setup walkthrough that adapts to your current state |
| oura_connection_status | verify local setup before calling Oura |
| oura_data_inventory | inventory supported data domains, scopes, privacy modes and recommended first calls without calling Oura APIs. |
| oura_daily_summary | readiness, sleep, activity and SpO2 brief for today |
| oura_weekly_summary | scorecard, comparison vs prior week, next-week plan |
{
"mcpServers": {
"oura": {
"command": "npx",
"args": ["-y", "oura-mcp-unofficial"]
}
}
}Configuration as documented by the project. Restart the client after saving.
http://127.0.0.1:3000/callback| Variable | Description | Required |
|---|---|---|
| OURA_CLIENT_ID | Configuration value read at startup. | Optional |
| OURA_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| OURA_TOKEN_PATH | Credential the server authenticates with. | Yes |
| OURA_CACHE_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.