Labsco
MCP SERVER

Chia Health MCP Server

by chia-health ↗

Run a US telehealth prescription flow — browse, intake, consent, order, pay — inside the conversation.

ERP & Vertical Business Systems
Summary
The token scope is the safety design.

Nothing sensitive is reachable until an email has been proven, and nothing in the patient portal is reachable until a payment has cleared — the same tool set behaves differently depending on which scope the token carries. Two things to plan for: rate limits are per category (auth is the tightest at 5/min), and `consent.text` returns text the agent is expected to present word for word rather than summarise.

What it is

A remote MCP server for the Chia Health telehealth platform. Browsing medications, the medical questionnaire, the consent documents, the order and the payment all happen through tool calls, and a licensed US provider reviews the intake before anything is dispensed.

What you get
  • Public browsing with no account at all — `medications.list`, `medications.details`, `medications.availability`, `medications.pricing`, `medications.categories`
  • A pre-screen on age, state, BMI and conditions through `eligibility.check`, and the structured questionnaire through `intake.questions`
  • Email verification that issues a guest-scoped token — `auth.start`, `auth.verify_otp`, `auth.resend_otp`, `auth.check_payment`
  • The five consent documents an intake requires, presented verbatim — `consent.list`, `consent.text`, `consent.submit`, `consent.status`
  • Ordering and ID verification — `order.create`, `order.status`, `order.documents`, `order.upload`
  • Two payment paths — `checkout.complete` takes a Stripe Shared Payment Token in-conversation, `checkout.create` returns a payment link the patient opens instead
  • After payment, portal access — `portal.log_weight`, `portal.log_side_effects`, `portal.message`, `portal.care_plan`, `portal.refill`, `portal.support`
  • Follow-up questions from the reviewing provider — `provider.questions`, `provider.respond`
Requirements

Nothing to install: it is a remote server at `https://mcp.chia.health/` over Streamable HTTP, published as doctormcp version 1.0.0, with metadata at `https://mcp.chia.health/server.json`. Any client that speaks Streamable HTTP connects with just the URL. Discovery and eligibility need no credentials; intake onward needs a guest bearer token obtained by verifying a patient email with a 6-digit OTP, and the portal tools need that token upgraded to full scope after payment.

Setup effort

One command — npx -y mcp-remote https://mcp.chia.health/