---
title: Hosted Delx Wellness MCP setup
description: Connect an AI agent to the hosted Delx Wellness Cloud MCP beta with an endpoint, API key, public tools, plan gates and a safe capabilities smoke call.
canonical: https://wellness.delx.ai/docs/cloud
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Hosted Delx Wellness MCP setup

The hosted hub exposes a Streamable HTTP MCP POST endpoint for beta users:

```text
https://api.delx.ai/wellness-hub/mcp
```

The logged-in product app is available at:

```text
https://wellness.delx.ai/app
```

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

## Short answer

Connect a remote MCP agent in four explicit checks: request beta access, create a
scoped API key, configure the Streamable HTTP POST endpoint and call
`wellness_capabilities` before reading provider data. Hosted OAuth is available
for configured providers; checkout and unavailable provider paths remain closed.

## Authentication

Use an API key in the Authorization header:

```text
Authorization: Bearer vital_live_your_key
```

API key secrets are shown once. The hosted hub stores hashes only.

## Smoke call

```bash
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`

## Common 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.

### 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 `wellness_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.

The hosted beta is available by request. Checkout is not live yet. Request access at https://wellness.delx.ai/pricing#founding-access.