Oura + ChatGPT

Connect Oura to ChatGPT with HealthSource

HealthSource is the permissioned bridge between your Oura Ring and ChatGPT. Authorize Oura once, and HealthSource turns provider-processed sleep, readiness, activity, workout, HRV, resting-heart-rate, and related signals into read-only, source-cited body context for ChatGPT.

Create a HealthSource account See the connection steps

Connection guide

How to connect Oura to ChatGPT

This Oura AI integration uses two separate OAuth permissions: one for HealthSource to read your authorized Oura signals and one for ChatGPT to request bounded HealthSource context. Neither connection exposes your password or provider access token to ChatGPT.

Create or sign in to HealthSource.Start with your HealthSource web account so every authorization and result stays attached to the correct user.
Connect Oura in your HealthSource account.Choose Oura under wearable sources and approve the read-only Oura OAuth request. You never give HealthSource or ChatGPT your Oura password.
Connect HealthSource in ChatGPT.When HealthSource app or connector access is available to your ChatGPT account, authorize HealthSource OAuth. The live data path is HealthSource's public OAuth MCP endpoint.
Ask for recovery context.Request a Daily Brief, recent measurements, body context, or connection status. HealthSource returns bounded, source-cited context from the wearable source you authorized.

Availability note: the HealthSource-to-ChatGPT OAuth data path is live. OpenAI directory review separately controls public listing and normal-user discovery inside ChatGPT.

What ChatGPT can receive

Processed wearable context.

Sleep and readiness context.
Activity and workout context.
HRV/RMSSD, resting heart rate, temperature deviation, SpO2, and stress context when available.
HealthSource recovery status, suggested action, confidence, and missing-data notes.

What stays out

Credentials and unrestricted records.

No Oura password or OAuth token is exposed to ChatGPT.
No claim of true raw sensor-data access.
No advertising, resale, model training, fine-tuning, or benchmarking use.
No diagnosis, treatment, medication, or emergency guidance.

Other supported AI paths

Connect HealthSource to your AI

ChatGPT is the primary consumer connection described here. HealthSource also publishes provider-neutral, read-only integration paths for approved Claude, Gemini, Grok, Perplexity, and API use.

ChatGPT

MCP endpoint: https://healthsource.app/mcp/public.
Users create or sign in to HealthSource, connect Oura or Withings with provider OAuth, then authorize HealthSource in ChatGPT when app or connector access is available.
This public OAuth MCP endpoint is how HealthSource feeds permissioned data into ChatGPT. OpenAI review separately controls directory publication and normal-user discovery.

Claude

Remote MCP connector URL: https://healthsource.app/mcp/public.
Claude custom connector setup: add HealthSource as a remote MCP connector, let Claude discover the OAuth metadata, authorize HealthSource, then connect Oura or Withings when prompted.
This is the direct Claude custom-connector path; Anthropic directory publication is a separate discovery path. Local Claude Desktop can still use the stdio server for private development.

Gemini

Function declarations: https://healthsource.app/api/v1/tool-schemas/gemini.
OpenAPI spec: https://healthsource.app/openapi.json.
Gemini schemas are published for developer integration. Production use requires HealthSource user authorization and compliance with Oura and platform terms.

Grok

Grok remote MCP URL: https://healthsource.app/mcp/public.
xAI/Grok function-tool fallback schema: https://healthsource.app/api/v1/tool-schemas/grok.
Grok can use HealthSource directly through xAI remote MCP where available, or through app-side function calling when the developer wants to execute HealthSource API calls themselves.

Perplexity

Perplexity tool schema: https://healthsource.app/api/v1/tool-schemas/perplexity.
Perplexity is a developer function-calling integration target; HealthSource does not claim a consumer marketplace listing.
The default packet is model-ready and omits raw debug endpoints.

API

OpenAPI spec: https://healthsource.app/openapi.json.
Core endpoints: /api/v1/recovery/today, /api/v1/body-context, /api/v1/analysis-packet, /api/v1/daily-brief.
Authorization: Bearer <HealthSource user access token>. Third-party production use requires explicit HealthSource user authorization and compliance with provider and platform terms.

FAQ

Oura and ChatGPT questions

Can ChatGPT read my Oura Ring data?

Yes, through HealthSource after you authorize both your HealthSource account and your Oura connection. HealthSource provides read-only, source-cited recovery and body context rather than your Oura password or access token.

What is an Oura AI integration?

An Oura AI integration lets an authorized AI client use bounded context derived from your Oura data. HealthSource connects Oura to ChatGPT through separate OAuth permissions and returns read-only, source-cited recovery and body context.

Does HealthSource send raw Oura sensor data to ChatGPT?

No. Oura provides processed wearable signals, provider-derived scores and metrics, and limited sampled physiological signals. HealthSource turns the authorized signals into bounded recovery and body context; it does not claim true raw sensor access.

Do I need to give ChatGPT my Oura password?

No. Oura authorization uses OAuth, and ChatGPT authorizes HealthSource separately. Passwords and provider access tokens are not exposed to ChatGPT.

Is HealthSource medical advice?

No. HealthSource is limited to wellness, recovery, fitness, performance reflection, and training readiness. It does not diagnose, treat, prescribe, or provide emergency guidance.