MCP server

PostHealth exposes a stateless MCP endpoint backed by the same account-scoped REST resources. Connect it to ChatGPT, Claude, or Gemini for sourced health summaries and comparisons.

Remote MCP

POST https://api.posthealth.dev/mcp
Authorization: Bearer fbt_live_...
Content-Type: application/json

Start with a tools request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Available tool families cover context, daily data, summaries, freshness, sleep, recovery, body, workouts, nutrition, glucose, correlations, and training logs.

Local bridge

For clients that cannot call remote HTTP MCP servers directly, use the repository's local stdio bridge:

cd mcp-server
npm install
export POSTHEALTH_API_KEY="fbt_live_..."
export POSTHEALTH_MCP_URL="https://api.posthealth.dev/mcp"
npm start

The bridge forwards read-only calls to PostHealth. It does not store health data locally.

Assistant boundary

MCP responses preserve source labels, date ranges, freshness, and caveats. The assistant can summarize and compare available data; it cannot diagnose conditions or turn derived values into official Fitbit, WHOOP, or Oura scores.