Chia Health MCP Server

Chia Health MCP Server

The official MCP (Model Context Protocol) server for Chia (Chia Health, Inc.), a US telehealth prescription platform. It lets AI assistants (ChatGPT, Claude, Gemini, Copilot and custom agents) help patients browse treatments, check eligibility, complete a medical intake, sign consent documents, place an order, pay, and manage their treatment, all in conversation.

Treatments include GLP-1 medications (semaglutide, tirzepatide, including tablets), peptide therapies (sermorelin, NAD+, glutathione) and longevity programs. Every prescription is evaluated by a licensed US provider and delivered from US-licensed 503A compounding pharmacies that source their ingredients solely from FDA-regulated sources, to all 50 states plus DC. Chia Health is LegitScript-certified, and patient support is available 24/7.

Prices: current plans and prices are on chia.health, and the medications_list, medications_details and medications_pricing tools always return the live prices. This README does not list prices.

Getting Started

Chia is a remote MCP server: connect over the network, no local installation required.

Server URL: https://mcp.chia.health/ Transport: Streamable HTTP Metadata: https://mcp.chia.health/server.json

{
  "mcpServers": {
    "chia-health": {
      "url": "https://mcp.chia.health/"
    }
  }
}

{
  "mcpServers": {
    "chia-health": {
      "url": "https://mcp.chia.health/"
    }
  }
}

{
  "mcpServers": {
    "chia-health": {
      "url": "https://mcp.chia.health/"
    }
  }
}

{
  "mcpServers": {
    "chia-health": {
      "serverUrl": "https://mcp.chia.health/"
    }
  }
}

Verify Connection

Once connected, your AI assistant can call these public tools right away (no auth required):

medications_categories     → treatment categories
medications_list           → all medications with current pricing
medications_availability   → check if a medication ships to your state
eligibility_check          → pre-screen age, state, BMI

What Can Your AI Assistant Do?

* Auth tools use a session_id (no token), except auth_check_payment, which uses a bearer token.

Important: Every prescription is evaluated and approved by a licensed US provider. This server handles the patient workflow; it does not make clinical decisions.

Authentication

Patients can browse freely without signing in: discovery, eligibility and the intake question preview are all public.

When the patient is ready to start their medical intake, they verify their email:

1. auth_start(email, phone, first_name) → sends a 6-digit code to their email, returns a session_id
2. auth_verify_otp(session_id, code) → returns a guest-scoped bearer token

The guest token covers intake, consent, ordering and checkout. After payment, auth_check_payment upgrades the token to full scope for portal access (care plan, messaging, refills).

Tool Catalog

Auth

Discovery (public, no auth)

Qualification (public + guest)

Consent (guest token required)

Ordering (guest token required)

Checkout (guest token required)

Patient Portal (full token required, after payment)

Provider (guest token required)

Example Agent Flows

1. Browse Medications (no auth)

User: "What weight loss medications do you offer?"

Agent calls: medications_list
→ Categories with semaglutide, tirzepatide, etc., and current prices

Agent calls: medications_details(medication="semaglutide-injectable")
→ Available plans with their current prices

Agent calls: medications_availability(medication="semaglutide-injectable", state="TX")
→ { "available": true }

Agent calls: eligibility_check(age=35, state="TX", bmi=31.2)
→ { "eligible": true, "available_medications": [...] }

2. Full Ordering Flow (verify → intake → consent → order → pay)

== VERIFY IDENTITY ==

1. auth_start(email="patient@example.com", phone="5551234567", first_name="Jane")
   → { "session_id": "abc123...", "otp_sent": true }

2. auth_verify_otp(session_id="abc123...", code="847293")
   → { "guest_token": "mcp_...", "scope": "guest" }

== MEDICAL INTAKE ==

3. intake_questions(medication="semaglutide-injectable")
   → Structured questionnaire (demographics, vitals, medical history, etc.)
   → Agent asks one section at a time

4. intake_submit(patient_email, patient_name, answers, bearer_token)
   → { "intake_id": "42", "next_step": "get_required_consents" }

5. consent_list(intake_id="42", bearer_token)
   → Consent documents (telehealth, treatment, pharmacy, HIPAA, AI disclosure)

6. For each consent:
   a. consent_text(consent_id, bearer_token)
      → Full text the agent MUST present verbatim
   b. Patient confirms: "I agree"
   c. consent_submit(intake_id, consent_id, "I agree", bearer_token)

== ORDER & PAY ==

7. order_create(intake_id, medication, form, plan_months, shipping_address, bearer_token)
   → { "order_id": "99", "total": "<current price>", "next_step": "create_checkout" }

8. checkout_create(order_id="99", bearer_token)
   → { "checkout_id": "7", "payment_url": "https://chia.health/..." }
   → Agent shares the link with the patient; it is also sent by email and SMS

9a. (ACP path) checkout_complete(checkout_id="7", shared_payment_token="spt_...", bearer_token)
    → { "payment_status": "success", "confirmation_number": "CHIA-000099" }

9b. (Fallback) Patient opens payment_url in a browser and pays on the Chia checkout page

10. auth_check_payment(bearer_token)
    → { "paid": true, "scope": "full" }  // token upgraded, portal unlocked

3. Patient Portal (full token, after payment)

1. portal_log_weight(patient_id, weight_lbs=195.5, date="2026-06-15", bearer_token)
   → { "recorded": true }

2. portal_care_plan(patient_id, bearer_token)
   → Current medication, phase, dosing schedule, recent weights

3. portal_log_side_effects(patient_id, effects=["nausea"], severity="mild", bearer_token)
   → { "recorded": true, "flagged_for_review": false }

4. portal_message(patient_id, message="Nausea improving", bearer_token)
   → { "sent": true }

Stripe ACP Integration

Chia supports Stripe's Agentic Commerce Protocol (ACP):

1. Order creation: order_create calculates the total from current prices and creates a pre-payment order.
2. Checkout: checkout_create creates a Stripe PaymentIntent (for ACP) and an authenticated payment link that signs the patient in and opens the Chia checkout page. The link is also sent by email and SMS.
3. Payment, two paths:
   • ACP: checkout_complete accepts a Shared Payment Token (SPT) from the AI platform and confirms the PaymentIntent. Instant, in-conversation payment.
   • Fallback: the agent shares the payment_url, the patient pays in their browser, and the agent polls auth_check_payment to detect completion.
4. After payment: the subscription and treatment enrollment are created automatically, and auth_check_payment upgrades the agent's token to full scope for portal access.

HIPAA Compliance

• Audit logging: every access to protected health information (PHI) is logged with actor, action, resource, IP address and timestamp. Logs are retained for 10 years.
• Consent records: every consent confirmation stores the verbatim confirmation text, method (AI agent conversation), platform, session ID and IP address. Consent records cannot be deleted.
• Input validation: all inputs are validated and sanitized; control characters are stripped, lengths enforced, and email, state, phone and ZIP formats checked.
• Email verification first: email ownership is verified with a 6-digit code before any patient data is accessed. Tokens are SHA-256 hashed and scoped (guest / full).
• Rate limiting: per-user and per-category limits (public: 100/min, sign-in: 5/min, authenticated: 30/min, consent: 10/min, checkout: 5/min).
• Minimal data exposure: tools return only what the current step needs. Payment details and full SSNs are never returned.

Support

• Issues: github.com/chia-health/chia-mcp/issues
• Website: chia.health
• Email: engineering@chia.health

License

Apache License 2.0. See LICENSE for details.

Copyright 2026 Chia Health, Inc.