Connect VitalTrends to ChatGPT
Add the hosted VitalTrends MCP server to ChatGPT on the web as a custom MCP app, sign in with your VitalTrends API key, and ask ChatGPT about your WHOOP, Oura, Withings, Apple Health, glucose, Hevy and Training Log data.
Server URL: https://mcp.vitaltrends.net/mcp
TL;DR
- On chatgpt.com, open Plugins, select +, then Add custom MCP server.
- Name it
VitalTrends, enterhttps://mcp.vitaltrends.net/mcp, choose OAuth, accept the risk warning and select Create as a plugin. - Install it, paste your VitalTrends API key on the Connect VitalTrends page and select Connect.
- In a new chat, type
@, pick VitalTrends and ask a question.
Requirements
- An active VitalTrends subscription.
- At least one data source connected and synced in Settings → Connections.
- Your personal API key from Settings → Developer. Turn on Allow workout write access only if you want ChatGPT to create or edit workouts.
- ChatGPT on the web at chatgpt.com. OpenAI says custom MCP servers can't be connected in the mobile apps.
- A ChatGPT plan or workspace that allows custom MCP servers. See Plan availability. In a Business workspace, an admin or owner usually has to create and publish the app.
Setup
These steps follow OpenAI's current help center and developer docs, checked 21 November 2026. Labels may differ by plan or workspace.
Go to chatgpt.com/plugins. Select the plus button (+), then Add custom MCP server. On some accounts the option is called Create MCP App. If you see neither, see Troubleshooting.
Enter VitalTrends as the name. Optionally add a description such as "My WHOOP, Oura, Withings, Apple Health, glucose and Training Log data". Under Connection, enter https://mcp.vitaltrends.net/mcp as the Server URL. Don't use Tunnel.
Under authentication, choose OAuth. Leave any client ID and client secret fields empty: VitalTrends registers ChatGPT automatically (dynamic client registration).
Review OpenAI's risk warning, tick I understand and want to continue, and select Create as a plugin. ChatGPT lists the VitalTrends tools it found. Check that names such as get_summary and get_whoop_daily are there.
Install the new plugin from your personal plugins (or the workspace where you created it). When ChatGPT asks you to sign in, the Connect VitalTrends page opens. It names the app asking for access. Paste your API key. Leave Allow changes to my Training Log unticked for read-only access, or tick it if you want ChatGPT to create and edit workouts. Select Connect.
Start a new chat, type @, select VitalTrends, and ask: "Use VitalTrends to summarize my last 7 days of sleep and recovery."
ChatGPT never sees your API key, only a token tied to it. The connection renews itself.
Business and Enterprise workspaces may still use the older admin path: Workspace settings → Apps → Create, enter the URL, choose OAuth, select Scan Tools, then Create. An admin then publishes the app so members can use it.
Select VitalTrends in a chat
- Type
@in the prompt box and choose VitalTrends. The app selection applies only to that message. Mention VitalTrends with@again when a follow-up needs new data. - Name the app in your prompt: "Use VitalTrends ...". To stop ChatGPT using web search instead, add "Use only the VitalTrends app."
- You can combine VitalTrends with other apps in the same prompt.
- To see what was sent and returned, expand the tool call in the reply. ChatGPT shows the full JSON input and output.
Plan availability
Checked 21 November 2026 against OpenAI's help article Connecting custom MCP servers in ChatGPT. OpenAI changes these limits often, so check that article for the current rules.
| ChatGPT plan | Add VitalTrends as a custom MCP server | Read your data | Training Log changes | Web | Mobile apps |
|---|---|---|---|---|---|
| Free, Go | Not listed by OpenAI | Not listed | Not listed | - | No |
| Plus | Not listed in the help article | Not listed | Not listed | - | No |
| Pro | Yes | Yes | No (read/fetch only) | Yes | No |
| Business | Admins and owners create and publish; members use the published app | Yes | Yes, with confirmation | Yes | No |
| Enterprise, Edu | Admins, or members an admin allows through role-based access | Yes | Yes, with confirmation | Yes | No |
- OpenAI says full MCP support (read and write) is only for Business, Enterprise and Edu. Pro can connect custom MCP servers with read/fetch permissions only.
- Deep research can use custom apps for read/fetch actions only, on every plan.
- VitalTrends has not tested each plan. Our verified run on 21 November 2026 did not record which plan was used.
Why the connector may be read-only
The VitalTrends connection is read-only by default. ChatGPT can create, edit or delete Training Log workouts only when all of these are true:
- Your ChatGPT plan allows writes. On Pro, custom MCP servers are read/fetch only, so the 14 write tools won't run.
- You ticked "Allow changes to my Training Log" on the Connect VitalTrends page.
- Your API key has "Allow workout write access" in Settings → Developer.
- The write tools are switched on in ChatGPT. Workspace admins can turn individual actions off. After a tool refresh, new actions start disabled until an admin enables them.
- You're not in deep research, which only uses read/fetch actions.
Daily brief and weekly review
OpenAI's scheduled tasks help article (checked 21 November 2026) says tasks can use supported apps such as Gmail, Slack and GitHub. It does not say tasks can use custom MCP apps like VitalTrends, and VitalTrends has not tested it. You can still run these prompts by hand in a chat with VitalTrends selected:
Daily brief
Weekly review
For a schedule that doesn't depend on ChatGPT tasks, use the Responses API script below with cron, or see Automations.
Responses API (developers)
The OpenAI Responses API can call the VitalTrends MCP server directly with the remote MCP tool ("type": "mcp"). Send your VitalTrends API key as a bearer header with headers. The API's authorization field is meant for OAuth access tokens, and OpenAI does not store either value, so send it with every request.
Set environment variables first:
export OPENAI_API_KEY="sk-..."
export VITALTRENDS_API_KEY="your-vitaltrends-api-key"
Python
import os
from openai import OpenAI
client = OpenAI() # reads OPENAI_API_KEY
resp = client.responses.create(
model="gpt-6.2-astra", # any current model that supports the MCP tool
store=False,
tools=[
{
"type": "mcp",
"server_label": "vitaltrends",
"server_description": "Synced WHOOP, Oura, Withings, Apple Health, glucose and Training Log data for one VitalTrends user.",
"server_url": "https://mcp.vitaltrends.net/mcp",
"headers": {"Authorization": "Bearer " + os.environ["VITALTRENDS_API_KEY"]},
# Import only the read tools this script needs.
"allowed_tools": ["get_summary", "get_whoop_daily", "get_oura_daily_readiness", "get_apple_health_daily"],
# Safe here because every allowed tool is read-only.
"require_approval": "never",
}
],
input="Summarize my sleep, recovery and resting heart rate for the last 7 days in five bullet points. No medical advice.",
)
print(resp.output_text)
curl
curl https://api.openai.com/v1/responses \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-d '{
"model": "gpt-6.2-astra",
"store": false,
"tools": [
{
"type": "mcp",
"server_label": "vitaltrends",
"server_description": "Synced WHOOP, Oura, Withings, Apple Health, glucose and Training Log data for one VitalTrends user.",
"server_url": "https://mcp.vitaltrends.net/mcp",
"headers": {"Authorization": "Bearer '"$VITALTRENDS_API_KEY"'"},
"allowed_tools": ["get_summary", "get_whoop_daily", "get_oura_daily_readiness", "get_apple_health_daily"],
"require_approval": "never"
}
],
"input": "Summarize my sleep, recovery and resting heart rate for the last 7 days in five bullet points. No medical advice."
}'
How it works and what to watch:
- The response contains an
mcp_list_toolsitem (the imported tools) and onemcp_callitem per tool call, with arguments, output and any error. require_approvaldefaults to"always". With approval required, the response containsmcp_approval_requestitems. Approve each one in a new request with anmcp_approval_responseinput item ("approve": trueand theapproval_request_id), chained withprevious_response_id.- If you allow write tools, keep approvals on for them. For example
"require_approval": {"never": {"read_only": true}}skips approval for read-only tools and still asks for the rest. Writes also need an API key with workout write access. allowed_toolskeeps cost and latency down. VitalTrends exposes 44 tools; importing all of them uses more tokens. See the tool reference.store=Falsestops OpenAI keeping the response for later retrieval. Data sent to OpenAI follows OpenAI's API data policies. See AI access and your data.- Keep both keys out of source control. Anyone with your VitalTrends API key can read your data.
If you only need numbers, not an AI summary, call the REST API directly.
First 5 prompts to try
All of these only read data.
- "@VitalTrends Summarize my last 7 days of sleep, recovery and HRV in a table by day."
- "@VitalTrends Compare my average resting heart rate this month with last month. Say which source each number came from."
- "@VitalTrends Show my Withings weight trend over the last 90 days with weekly averages."
- "@VitalTrends List my workouts from the last 14 days from the unified workout feed, with duration and source."
- "@VitalTrends Show my Training Log volume by muscle group for the last 30 days."
More ideas: Prompt library. ChatGPT's answers are not medical advice. Talk to a clinician about health decisions.
Limits
- Web only. OpenAI says custom MCP servers are web only. Don't expect VitalTrends in the ChatGPT mobile apps.
- Plan limits. Pro is read/fetch only. Business members need an admin to publish the app. See Plan availability.
- One message at a time. Selecting VitalTrends with
@applies to that message only. - Not everything is available. Lab reports, weekly recaps, Control Center, provider connections, billing and account settings are website-only. ChatGPT can't read your lab results through VitalTrends.
- Large results. Long date ranges can return a lot of data. Ask for a shorter range if ChatGPT says a result is too large.
- Tool updates. When VitalTrends adds or changes tools, ChatGPT doesn't update automatically. Refresh the app (see Troubleshooting).
- Privacy. Data ChatGPT reads is handled under OpenAI's privacy policy. See AI access and your data.
Troubleshooting
"Add custom MCP server" is missing
Check your plan in Plan availability. On Business, ask an admin or owner to add and publish VitalTrends; members may see "You need workspace admin permission". On Enterprise and Edu, an admin can grant permission to create custom MCP servers. OpenAI no longer requires a separate developer mode, but if your account still shows Developer mode under Settings → Security and login, turn it on and reload Plugins.
Tool not found, or VitalTrends tools not exposed
- Start a new chat, type
@and select VitalTrends. Mention it again in follow-ups. - Refresh the tool list: open VitalTrends in ChatGPT Plugins and select Refresh. In Business and Enterprise workspaces an admin refreshes it in Workspace settings → Apps (the ••• menu, then Action control), and new actions start disabled until an admin turns them on.
- Reconnect: remove the VitalTrends app, add it again, and sign in with your API key.
ChatGPT searches the web instead
Add "Use only the VitalTrends app" to your prompt.
Read-only
See Why the connector may be read-only. To change the consent choice, remove the app, add it again and tick Allow changes to my Training Log.
Invalid key
Copy the full key without spaces, or regenerate it in Settings → Developer. The key must belong to an account with an active subscription.
Asked to sign in again
The API key behind the connection was deleted or regenerated, or the connection went unused for about six months. Reconnect with your current key.
No data
Check that a source is connected and synced, and that the key comes from the same VitalTrends account.
More: MCP Server troubleshooting.
FAQ
How is this different from ChatGPT Health?
ChatGPT Health is OpenAI's own health space in ChatGPT. As of 21 November 2026, OpenAI's help article says it is for Free, Go, Plus and Pro users in the U.S. It connects Apple Health (iOS), Health Connect (Android), supported U.S. provider portals for medical records, One Medical and Function Health. WHOOP, Oura, Garmin, Strava and MyFitnessPal reach it through Apple Health or Health Connect.
VitalTrends works differently:
- It reads WHOOP, Oura, Withings and Hevy from their own APIs, so ChatGPT gets provider data such as WHOOP recovery, strain and sleep stages or Oura readiness, plus Apple Health, glucose (CGM) and your Training Log. It doesn't depend on what each app writes to Apple Health or Health Connect.
- It works anywhere ChatGPT allows custom MCP servers, and in other AI apps such as Claude, Codex and Grok, with the same data.
- With write access, ChatGPT can edit your Training Log.
ChatGPT Health can also read medical records from supported U.S. providers. VitalTrends can't: lab results stay on the VitalTrends website and are not available through MCP. You can use both.
Do I need developer mode?
OpenAI's current docs add custom MCP servers from Plugins without a separate developer mode. Some accounts still show a Developer mode setting under Settings → Security and login. Turn it on if Add custom MCP server doesn't appear.
Does ChatGPT see my API key?
No. You paste the key on the VitalTrends page, and ChatGPT only receives a token tied to it. Delete or regenerate the key in Settings → Developer to cut off access.
Can ChatGPT change my data?
Only your Training Log, and only if your plan allows writes, you ticked Allow changes to my Training Log, and your key has workout write access. ChatGPT asks for confirmation before write actions by default.
Can I use it on my phone?
OpenAI says custom MCP servers are web only. Use chatgpt.com in a browser.
Is VitalTrends in the ChatGPT app directory?
Not yet. Add it as a custom MCP server as described above.
How do I disconnect?
Remove the VitalTrends app in ChatGPT Plugins. To revoke access everywhere, delete or regenerate your API key in Settings → Developer.