ChatGPT

Use Betterness alongside ChatGPT — connector, Custom GPT, or CLI bridge.

Current status

OpenAI supports remote MCP through developer-mode connectors and API integrations. Availability depends on your ChatGPT plan, workspace settings, and connector permissions.

Option 1 — ChatGPT MCP connector

If your workspace has developer-mode connectors enabled:

Endpoint:      https://api.betterness.ai/mcp
Authorization: Bearer bk_your_token_here

Add this in Settings → Connectors → New connector. Read-only health questions work everywhere; for purchases, appointments, or clinical decisions, keep the user in the loop.

Option 2 — CLI + copy-paste

Run the CLI locally and paste output into ChatGPT:

betterness workflow daily-brief --json
betterness biomarkers search --range OUT_OF_RANGE --json
betterness activity get --from 2026-03-01 --json

Then in ChatGPT: "Here are my latest biomarker results — which should I be concerned about?"

Option 3 — Custom GPT with API key

Build a Custom GPT that calls Betterness REST endpoints directly:

Generate an API key at /console/keys
Create a Custom GPT
Add Actions that call https://api.betterness.ai endpoints with the API key as a Bearer token
Configure the GPT's instructions for responsible health-data handling

Option 4 — OpenClaw with ChatGPT backbone

Use BetterClaw with the OpenAI API as your LLM, connecting to Betterness MCP for health context. Best for autonomous agents.

Cautions

Connector availability depends on plan and workspace settings — check before deploying broadly.
Never paste long-lived tokens into shared chats, screenshots, or public GPT instructions.
Purchases, bookings, exports, and clinical decisions should remain user-confirmed.

Windsurf OpenClaw / BetterClaw