All studies
Research·November 3, 2026·4 min read

Which AI Assistants Can You Connect HealthOS To

Claude connects to your own health data via custom connector on claude.ai, desktop and mobile. ChatGPT, Perplexity, Mistral and Grok accept custom connectors; Gemini and Copilot do not.

Which AI assistants can you connect HealthOS to? Claude today, with a custom connector on claude.ai, the desktop app and the mobile apps. ChatGPT, Perplexity, Mistral and Grok also accept custom connectors, so the same MCP endpoint can be added there, but the product is not listed in their directories unless this page says so. Gemini and Microsoft Copilot have no personal connector option yet.

Which assistants can I connect to my own data?

Claude is the assistant with a step-by-step setup guide on the connector page today. To set it up in Claude, open Settings > Connectors > Add custom connector, name it, paste the URL, sign in, tick scopes, then switch the connector on in a new chat's tools menu. Custom connectors work on every Claude plan. On Team and Enterprise plans an owner may have to add the connector for the organisation first.

Assistants and custom connector status
AssistantConnection todayWhat to do
ClaudeYesSettings > Connectors > Add custom connector, then paste the MCP URL
ChatGPTCustom onlyAdd the MCP URL as a custom connector if your interface allows it
PerplexityCustom onlySame MCP URL, manual setup
MistralCustom onlySame MCP URL, manual setup
GrokCustom onlySame MCP URL, manual setup
GeminiNoNo personal connector option today
Microsoft CopilotNoNo personal connector option today

Scroll the table sideways for the rest →

Status as the connector page describes it today.

The thing people get wrong is looking for this connector in a directory inside Claude or ChatGPT. You are not searching a catalogue. You add it as a custom connector with one URL.

The connection shares only what you tick. Reading starts on; writes, DNA, delete and account changes start off.

How the connection actually works

This is MCP over OAuth 2.1, not a file export and not a password handover. You paste the connector URL https://mcp.healthosx.com/mcp, sign in to your account, and approve a token. The endpoint uses OAuth 2.1 with PKCE S256, but you just see a sign-in screen. The token lasts 1 hour. Refresh tokens rotate on every use, and the whole connection lasts up to 365 days before it asks you to approve again.

What happens when you connect
You paste the connector URL
https://mcp.healthosx.com/mcp
You sign in and tick scopes
Reading is on by default
You approve or deny writes
Logging, DNA and delete stay off unless ticked
Assistant gets an OAuth token
Access token lasts 1 hour
It reads only ticked data
No raw genome, no payment tools
Destructive tools ask first
Delete and share need confirmation

Because each tool call maps to one API operation, the same scope checks apply every time. An assistant cannot read your blood tests in one question and then quietly write a weight entry later, unless you separately ticked write.

What gets shared, and what stays off

The consent screen is the control point.

  • Reading is ticked by default: activity, sleep as synced from Apple Health, glucose, meals, blood tests and similar.
  • Everything else starts off: writing or logging data, DNA tools, ask features, community, export and account changes.
  • Deleting data needs a separate yes. Destructive actions refuse to run without confirmation.
  • Over OAuth, DNA tools return findings and lookups, never the whole genome.
  • Over OAuth, assistants get no checkout or payment tools.

In practice, if you want the assistant to log your weight or water, you tick that write family when you approve. If you never tick it, the assistant can read but cannot create entries.

Disconnect any time from Settings > Connected apps in the app or on the web. Access stops straight away.

ChatGPT, Perplexity, Mistral and Grok: same URL, less hand-holding

ChatGPT, Perplexity, Mistral and Grok accept custom connectors, so the same MCP URL can be added manually where the product allows one. Each product has a different place for custom connectors. If you cannot find a custom connector option, it is probably not available on your plan or interface. The connector page says an assistant is added there only after it has been tested end to end. Today that means Claude has the exact four-step guide. The others may work but are not yet presented as a tested path.

Gemini and Microsoft Copilot have no personal option today

Gemini and Microsoft Copilot do not give you a place to add a personal MCP custom connector. That means you cannot connect your own health data to them as an assistant right now. Both companies have enterprise AI platforms, but personal custom connector support is what matters here, and it is absent today. If you use one of those, you would need to switch to an assistant that accepts a custom connector or build your own agent with a personal token from the developer API.

Freshness, limits and the number that matters

Your assistant sees what the iPhone last synced. Health data carries meta.phone_last_sync_at, so the assistant can tell you exactly when that was. If a glucose or sleep answer looks stale, open the iPhone app and sync before asking.

Limits are per connection: 60 calls per minute and 2,000 tool calls per day UTC. That is enough for interactive questions and plotting, not for bulk re-processing every record you own. The daily limit is per connection, not per chat.

Wellness information is not medical advice. An assistant can be wrong, so check anything important with a doctor.

Set it up where it is already guided: the HealthOS connector page has the step-by-step Claude setup and the first questions to ask. Pick a question from your own data, not from averages.

Written by

HealthOS Research

Keep reading