Delx Wellness
Back to Cloud

Hosted MCP setup

Connect an agent to Wellness Cloud.

The hosted hub exposes a Streamable HTTP MCP endpoint for beta users who want remote wellness context without running the connector stack themselves.

Current status: accounts, remote MCP and hosted wearable OAuth are live for configured providers. Checkout is not live yet.

Request accessReview security

Current beta endpoint

MCP URL
https://api.delx.ai/wellness-hub/mcp
Dashboard
https://wellness.delx.ai/app
Auth
Authorization: Bearer vital_live_...

Short answer

Connect a remote MCP agent in four explicit checks.

Request beta access, create a scoped API key, configure the Streamable HTTP endpoint and call wellness_capabilitiesbefore reading provider data. The beta status is factual: hosted OAuth is available for configured providers, while checkout and unavailable provider paths remain closed.

Request beta access

The app, account flow, remote MCP endpoint and hosted wearable OAuth are live for configured providers. Checkout is not live yet.

Create an API key

Keys use the vital_test_ or vital_live_ prefix. Secrets are shown once; the hub stores hashes only.

Connect through Streamable HTTP MCP

Use the hosted /mcp Streamable HTTP POST endpoint with an Authorization bearer key from any compatible remote MCP client.

Verify plan gates

Public tools work with an API key. Premium tools such as wellness_today require an active Wellness Cloud plan.

Smoke call (POST)

Verify the hosted endpoint before wiring workflows.

Start with `wellness_capabilities`; it does not read provider data and returns the billing model, public tools and gated premium tools.

curl -s -X POST https://api.delx.ai/wellness-hub/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H 'authorization: Bearer vital_live_your_key' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "wellness_capabilities",
      "arguments": { "response_format": "json" }
    }
  }'

Public tools

wellness_capabilities
wellness_provider_status
wellness_privacy_audit
wellness_export_data
wellness_delete_data

Plan-gated tools

wellness_today
wellness_summary
health_recommend_workout
recommend_today_training
build_workout_from_recovery

FAQ

Hosted Wellness Cloud questions.

How do I connect an agent to Wellness Cloud MCP?

Request beta access, create a vital_live_ or vital_test_ API key in the product app, then send Streamable HTTP POST requests to https://api.delx.ai/wellness-hub/mcp with an Authorization bearer header. Start with wellness_capabilities before reading provider data.

Is Wellness Cloud checkout live?

No. Accounts, remote MCP and hosted wearable OAuth are live for configured providers, but checkout is not live yet. Access is currently handled as a beta request and plan gates remain explicit.

Which Wellness Cloud tools are public and which are plan-gated?

Public tools include wellness_capabilities, wellness_provider_status, wellness_privacy_audit, wellness_export_data and wellness_delete_data. wellness_today, wellness_summary and training recommendation tools are plan-gated.

Does the hosted MCP endpoint expose my OAuth token to the agent?

No. Provider credentials are held by the hosted hub and the agent receives bounded MCP responses. Use the security page and privacy_audit tool to inspect the current hosted controls.

Which wearable providers are available in the beta?

Hosted wearable OAuth is live for configured providers; the current public disclosure names WHOOP and Strava. Other providers remain unavailable until their credentials and provider path are configured.

Generic client config

Use the remote endpoint from any MCP client that supports Streamable HTTP.

{
  "mcpServers": {
    "delx-wellness-cloud": {
      "type": "http",
      "url": "https://api.delx.ai/wellness-hub/mcp",
      "headers": {
        "Authorization": "Bearer vital_live_your_key"
      }
    }
  }
}