Connect HealthSource to your AI

HealthSource is a read-only recovery and body-context service for approved, user-authorized AI integrations.

Boundary: wellness, recovery, fitness, performance reflection, and training readiness only. No diagnosis, treatment, medication, or emergency guidance.

Oura data-use boundary: Oura-derived data is used only to generate the user-requested HealthSource recovery context. It is not sold, used for advertising, used to train or fine-tune AI models, or redistributed as a provider-record feed. Third-party AI/platform integrations require user authorization and any required platform or Oura approval before production use.

ChatGPT

MCP endpoint: https://healthsource.app/mcp/public.
Users install/connect HealthSource, authorize HealthSource OAuth, then connect their own Oura account.
This path is gated by ChatGPT app approval, Oura app approval, and validation that Oura-derived data is not used for model training or unapproved redistribution.

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 when prompted.
This is the Claude product path after approval; 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 approval and implementation planning; production use requires user authorization plus Oura/platform approval.

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 future approved function-calling integration target.
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 approval before Oura-derived data is processed outside HealthSource.