Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
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"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The 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.
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.
Turn on the Vital connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
vital_list_users | read | List users List all Vital users in your team, paginated. Vital API: GET /v2/user. |
vital_get_user | read | Get user Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}. |
vital_resolve_user | read | Resolve user by client_user_id Look up a Vital user by your own client_user_id (the stable id you assigned). Vital API: GET /v2/user/resolve/{client_user_id}. |
vital_get_user_connected_providers | read | Get user's connected providers List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}. |
vital_get_user_latest_info | read | Get user's latest info Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest. |
vital_list_providers | read | List supported providers List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers. |
vital_get_sleep | read | Sleep Get sleep summaries for a user over a date range. Vital API: GET /v2/summary/sleep/{user_id}. |
vital_get_activity | read | Activity Get activity summaries for a user over a date range. Vital API: GET /v2/summary/activity/{user_id}. |
vital_get_workouts | read | Workouts Get workouts summaries for a user over a date range. Vital API: GET /v2/summary/workouts/{user_id}. |
vital_get_body | read | Body Get body summaries for a user over a date range. Vital API: GET /v2/summary/body/{user_id}. |
vital_get_meal | read | Meal Get meal summaries for a user over a date range. Vital API: GET /v2/summary/meal/{user_id}. |
vital_get_menstrual_cycle | read | Menstrual cycle Get menstrual cycle summaries for a user over a date range. Vital API: GET /v2/summary/menstrual_cycle/{user_id}. |
vital_get_profile | read | Profile Get a user's profile summary (height, and other static attributes). Vital API: GET /v2/summary/profile/{user_id}. |
vital_get_timeseries | read | Get timeseries data Get timeseries data points for a user and resource over a date range. Supported resources: heartrate, hrv, glucose, blood_pressure, blood_oxygen, steps, respiratory_rate, body_weight, body_fat, distance, water, vo2_max, stress_level, mindfulness_minutes, calories_active, calories_basal, floors_climbed, caffeine, cholesterol. Vital API: GET /v2/timeseries/{user_id}/{resource}. |
vital_list_lab_tests | read | List lab tests List the lab tests available/configured for your team. Vital API: GET /v3/lab_tests. |
vital_get_lab_test | read | Get lab test Get a single lab test by id. Vital API: GET /v3/lab_tests/{lab_test_id}. |
vital_list_orders | read | List orders List lab-test orders with filters, paginated. Vital API: GET /v3/orders. |
vital_get_order | read | Get order Get a single lab-test order by id. Vital API: GET /v3/order/{order_id}. |
vital_get_order_results | read | Get order results Get the lab-test results for an order. Vital API: GET /v3/order/{order_id}/result. |
vital_create_user | write | Create user Creates a Vital user record (additive). Returns the Vital user_id. Vital API: POST /v2/user. |
vital_create_link_token | write | Create link token Creates a short-lived Link token to connect a user's wearable/provider (no health data is modified). Vital API: POST /v2/link/token. |
vital_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
vital_request_feature | Request a missing feature Tell usefulapi that the user needs something the Vital tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
vital_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Vital tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
vital_cancel_subscription | Cancel the Pro subscription Cancel the caller's Vital Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run vital_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Vital server only. Subscribe with vital_upgrade (it returns a Stripe Checkout link). Cancel any time with vital_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running vital_upgrade before then undoes the cancel. Or write to [email protected].
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.
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 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Vital server only. Run vital_usage_status to see how many calls you used.
Ask the AI to run vital_upgrade: it returns a Stripe Checkout link. To cancel, run vital_cancel_subscription. Pro 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, 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.