Vital MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.36.4Updated Nov 7, 2026

Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableLocation & Lifestyle Data & Analytics

Server details

Identifier: io.usefulapi/vital
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fvital.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fvital?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Reads Vital wearable and lab health data — users, sleep, activity, workouts, timeseries and lab orders — from an MCP client.

What you can do: List, get and resolve Vital users, and see which wearables or providers each has connected
Read sleep, activity, workout, body, meal, menstrual cycle and profile summaries over a date range
Fetch timeseries points such as heart rate, HRV, glucose, steps and blood oxygen
List supported providers and lab tests, and read lab-test orders and their results
Create a user record or a short-lived Link token to connect a provider
Check monthly usage, request a feature, upgrade or cancel a plan
When to use it: Useful when you want an assistant to answer questions about your team's Vital users and their health data, such as recent sleep, workouts or lab results, without writing API calls yourself.
Requirements: Remote endpoint at vital.usefulapi.io over streamable HTTP; no local install. Sign-in uses OAuth, and the login page asks for your Vital API key, which is validated and stored per user. A Vital account with users and connected providers is needed for meaningful data.

Before you install

Handles sensitive health data, including menstrual cycle, lab results and body metrics, sent to the hosted service. The Vital API key is entered at sign-in and stored per user. Write tools create users and link tokens; confirm before running them. Usage is metered: 50 calls per month free, paid plans via a Stripe checkout link, and cancellation gives no refund for the current period.

Installation

In SourceWeft

Open Vital MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fvital/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vital-by-usefulapi": {
      "type": "http",
      "url": "https://vital.usefulapi.io/mcp"
    }
  }
}

README

Vital MCP by usefulapi

Read wearables and lab health data — sleep, activity, workouts, timeseries, and lab results — from Claude, Cursor, or any MCP client. Hosted, no local install — connect with your Vital API key.

Live endpoint: https://vital.usefulapi.io/mcp · Homepage: https://usefulapi.io/vital

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://vital.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http vital https://vital.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

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, and the login page asks for your Vital credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/vital/

On first connect you'll paste your Vital API key. It's validated, stored per-user, and scoped to you.

Tools

Tool	Type	What it does
`vital_list_users`	read	List users
`vital_get_user`	read	Get user
`vital_resolve_user`	read	Resolve user by client_user_id
`vital_get_user_connected_providers`	read	Get user's connected providers
`vital_get_user_latest_info`	read	Get user's latest info
`vital_list_providers`	read	List supported providers
`vital_get_sleep`	read	Sleep
`vital_get_activity`	read	Activity
`vital_get_workouts`	read	Workouts
`vital_get_body`	read	Body
`vital_get_meal`	read	Meal
`vital_get_menstrual_cycle`	read	Menstrual cycle
`vital_get_profile`	read	Profile
`vital_get_timeseries`	read	Get timeseries data
`vital_list_lab_tests`	read	List lab tests
`vital_get_lab_test`	read	Get lab test
`vital_list_orders`	read	List orders
`vital_get_order`	read	Get order
`vital_get_order_results`	read	Get order results
`vital_create_user`	write	Create user
`vital_create_link_token`	write	Create link token
`vital_usage_status`	meta	Usage status (free-tier meter)
`vital_request_feature`	meta	Request a missing feature
`vital_upgrade`	meta	Upgrade to Pro or Pro+
`vital_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this 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].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/vital/README.md at commit 4046075

Tools

vital_list_users

List users

List all Vital users in your team, paginated. Vital API: GET /v2/user.

Parameterslimitoffset

vital_get_user

Get user

Get a single Vital user by their Vital user_id. Vital API: GET /v2/user/{user_id}.

Parametersuser_idrequired

vital_resolve_user

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}.

Parametersclient_user_idrequired

vital_get_user_connected_providers

Get user's connected providers

List the wearables/data sources (providers) a user has connected. Vital API: GET /v2/user/providers/{user_id}.

Parametersuser_idrequired

vital_get_user_latest_info

Get user's latest info

Get the latest device/app info reported for a user. Vital API: GET /v2/user/{user_id}/info/latest.

Parametersuser_idrequired

vital_list_providers

List supported providers

List all providers (wearables/data sources) Vital supports. Vital API: GET /v2/providers.

Takes no parameters.