Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Vital connector, then ask in plain words. The AI picks the tools.
For developers who build health and fitness apps on wearable data and lab tests from Vital.
The AI lists the providers (wearables and data sources) one user has connected, and the latest device or app info for that user.
The AI reads sleep, activity and workout summaries for one user over a date range. It sums up the trend for you.
The AI reads timeseries points for one user and one resource, such as heartrate, hrv, steps or body_weight, over a date range. It can add the body summary.
The AI finds a Vital user by your client_user_id or by Vital user_id, and lists the users of your team.
The AI lists the lab tests available to your team and opens one test for its details.
The AI creates a Vital user and a short-lived link token, so the user can connect a wearable or provider.
Changes dataThe login page asks for your Vital API key and Region.
Find your key in the Vital / Junction dashboard → Settings → API keys, and pick the region that key belongs to (US, EU, or Sandbox). Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"vital": {
"url": "https://vital.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"vital": {
"type": "http",
"url": "https://vital.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Vital API key and Region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+ | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Vital server only. Ask your AI to run vital_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with vital_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with vital_upgrade before then undoes the cancel. Or write to [email protected].
vital_list_usersvital_get_uservital_resolve_uservital_get_user_connected_providersvital_get_user_latest_infovital_list_providersvital_get_sleepvital_get_activityvital_get_workoutsvital_get_bodyvital_get_mealvital_get_menstrual_cyclevital_get_profilevital_get_timeseriesvital_list_lab_testsvital_get_lab_testvital_list_ordersvital_get_ordervital_get_order_resultsvital_create_uservital_create_link_tokenvital_usage_statusvital_request_featurevital_upgradevital_cancel_subscriptionCheck which wearables a user has connected. Review sleep, activity and workouts for a user. Read wearable timeseries and body summaries. Find a user by id or list your team's users. Check which lab tests you offer. Create a user and a link token for a wearable. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Vital. The server calls the Vital API with your own Vital access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Vital API key and Region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Vital API key and Region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Vital API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Vital.
Yes, if you approve it. 2 of the 21 Vital tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Vital server only. Cancel any time: your paid plan then runs to the end of the paid period. Run vital_usage_status to see how many calls you used.
Ask the AI to run vital_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run vital_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with vital_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.