Oura MCP integration for AI agents.
Connect AI agents to Oura through 35 structured actions, including get daily activity, get daily cardiovascular age, and get daily readiness. Review authenti…
- ACTION CONTRACTS
- 35
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Oura integration exposes
The Oura Agent App exposes 35 provider-backed actions for data work. Its current contract lets an authorized agent get one daily activity summary document from oura by document id, get one daily cardiovascular age document from oura by document id, and get one daily readiness summary document from oura by document id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Oura account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Oura capabilities.
Showing 12 of 35 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_daily_activityREADGet one daily activity summary document from Oura by document ID.
INPUTS: documentId
get_daily_cardiovascular_ageREADGet one daily cardiovascular age document from Oura by document ID.
INPUTS: documentId
get_daily_readinessREADGet one daily readiness summary document from Oura by document ID.
INPUTS: documentId
get_daily_resilienceREADGet one daily resilience summary document from Oura by document ID.
INPUTS: documentId
get_daily_sleepREADGet one daily sleep summary document from Oura by document ID.
INPUTS: documentId
get_daily_spo2READGet one daily SpO2 summary document from Oura by document ID.
INPUTS: documentId
get_daily_stressREADGet one daily stress summary document from Oura by document ID.
INPUTS: documentId
get_enhanced_tagREADGet one enhanced tag document from Oura by document ID.
INPUTS: documentId
get_personal_infoREADGet personal information for the authenticated Oura account.
get_rest_mode_periodREADGet one rest mode period document from Oura by document ID.
INPUTS: documentId
get_ring_configurationREADGet one ring configuration document from Oura by document ID.
INPUTS: documentId
get_sessionREADGet one guided or unguided session document from Oura by document ID.
INPUTS: documentId
INPUT CONTRACTS
Know what the action needs before it runs.
get_daily_activity
documentIdREQUIRED- The Oura document identifier.
get_daily_cardiovascular_age
documentIdREQUIRED- The Oura document identifier.
get_daily_readiness
documentIdREQUIRED- The Oura document identifier.
get_daily_resilience
documentIdREQUIRED- The Oura document identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Daily Activity
Get one daily activity summary document from Oura by document ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_daily_activityVerify with Get Daily Cardiovascular Age
Get one daily cardiovascular age document from Oura by document ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_daily_cardiovascular_ageSAFETY BOUNDARY
Operate Oura with explicit limits
- Authorize Oura with OAuth 2.0 and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Oura data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `daily`, `heart_health`, `stress`, and `spo2`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Oura task completed successfully.
CONNECTION MODEL
OAuth 2.0
Oura uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 35
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Oura.