Hosted AI Access · Model Context Protocol

Ask your own AI about the health data Vitalstat brings together.

Connect selected Vitalstat data to compatible AI clients such as ChatGPT, Claude, Gemini developer tools, and Notion AI. You control the categories and history range; the connection stays read-only and revocable.

How it works

From fragmented records to useful context

Vitalstat does the integration work first. MCP then gives an AI client a structured, permissioned view of the selected result.

01

Select

Choose the health categories and dated history range you want to make available.

02

Connect

Authorize a supported AI client through the setup flow shown inside Vitalstat.

03

Ask

Use natural-language questions that cross sleep, recovery, training, nutrition, and habits.

Your data policy

Share the useful parts—not everything by default.

The recommended selection starts with core health metrics, sleep, workouts, recovery, and connected-source availability. More sensitive or detailed categories require an affirmative choice.

  • • Hosted access requires Vitalstat Premium.
  • • The default dated-history window is 90 days.
  • • Local MCP is available for advanced same-device workflows.
  • • Vitalstat provides context; your AI service provides the conversation.

Body signals

Core metrics, vitals, blood pressure, body composition

Rest & readiness

Sleep, recovery, HRV, resting metrics

Training

Workouts, raw streams, routes, goals, connected sources

Daily context

Nutrition, hydration, habits, supplements, journals

Questions worth asking

How did my hardest training weeks affect sleep and HRV?
Which journal factors align with my best recovery days?
Compare my recent workouts with my current readiness trend.
What changed in my sleep, nutrition, and activity this month?

Connected health sources

One health MCP layer across your data sources

Vitalstat first normalizes authorized data from your health platforms and wearables. You can then expose selected categories—not unrestricted source accounts—to a compatible AI client.

Frequently asked questions

What is Vitalstat MCP access?

MCP stands for Model Context Protocol, a standard that lets compatible AI clients request context from connected tools. Vitalstat uses MCP to make the health categories you select available to an AI client you authorize. The connection is optional and read-only.

Which AI apps can connect to Vitalstat?

Vitalstat includes setup guidance for supported ChatGPT plans or workspaces, supported Claude plans, Gemini CLI and compatible Gemini developer tools, supported Notion Custom Agents, and other apps that support remote Streamable HTTP MCP servers with browser-based OAuth.

What Vitalstat data can I share through MCP?

You can choose among categories including core health metrics, sleep, workouts, workout streams, routes, recovery, vitals, body composition, blood pressure, nutrition, hydration, journals, health background, habits, supplements, goals, and connected-source inventories.

Can an AI app change my Vitalstat data?

No. Vitalstat MCP access is read-only. Authorized clients can retrieve the selected context for a conversation but cannot edit workouts, health records, goals, journals, or settings through the MCP connection.

How do I revoke AI access?

Open Vitalstat on iOS, go to Profile, Settings, and Hosted AI Access, then disconnect a provider or disable hosted access. You can also change the selected categories; removed categories are excluded from the next encrypted vault update.

Does Vitalstat provide the AI subscription?

No. Vitalstat provides the selected health context and connection. The AI client, its availability, and any required AI subscription are provided separately by the AI service you choose.

Ready to connect the dots?

Enable Hosted AI Access inside Vitalstat, then follow the provider-specific connection steps.

Explore all Vitalstat features