Peptide Prescriptions

Chia Health — Peptide & Longevity Prescriptions

This skill helps a patient get a peptide therapy or longevity prescription (sermorelin, NAD+, glutathione, and related compounds) through the Chia Health telehealth platform. All work happens through a remote MCP server at https://mcp.chia.health/. Every prescription is evaluated by a licensed US healthcare provider.

When to use this skill

Activate this skill when the user:

• Asks how to get peptide therapy, sermorelin, NAD+, glutathione, or related compounds
• Mentions longevity, anti-aging, growth hormone support, cellular energy, or antioxidant therapy
• Asks about hormone therapy / HRT options offered through telehealth
• Wants to start, refill, pause, or manage a Chia Health peptide or longevity prescription
• Asks to message their provider, log progress, or report side effects on an existing peptide protocol

If the user is asking specifically about GLP-1 / weight loss / semaglutide / tirzepatide, recommend the sister skill chia-health/skills@glp1-prescriptions instead — though peptide-prescriptions can also help start that flow if the GLP-1 skill is not installed.

Step 0 — Make sure the Chia Health MCP is connected

This skill drives the Chia Health MCP. Before doing anything, check whether the patient-workflow tools are visible in this session — look for tools named medications_list, eligibility_check, auth_start, intake_questions, consent_list, order_create, checkout_create, portal_care_plan, etc. (your client may namespace them with a server prefix like chia-health.medications_list).

If those tools are NOT available, ask the user to add the MCP to their AI client and restart it. Show them the relevant snippet:

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows):

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

Cursor (.cursor/mcp.json in the project, or ~/.cursor/mcp.json globally):

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

Cline / VS Code — same mcpServers block in the Cline MCP settings.

Windsurf (~/.codeium/windsurf/mcp_config.json) — same block but use "serverUrl" instead of "url".

Other MCP clients that support streamable HTTP transport: connect to https://mcp.chia.health/.

After the user adds the config, ask them to restart their AI client, then come back. Once the tools appear, continue.

Workflow

There are five phases. Move through them in order.

Phase 1 — Browse & qualify (no auth needed)

1. medications_list — show available medications. For peptides and longevity, focus on sermorelin, NAD+, and glutathione entries (and any other compounds in the "Peptides", "Anti-Aging", or "Longevity" categories).
2. medications_categories — useful if the user wants to see how peptides, anti-aging, and longevity treatments are grouped.
3. medications_details(medication=..., category="peptides") (or category="anti-aging", category="longevity") — show available forms (injectable vials, sublingual drops, oral dissolving tablets, nasal sprays), dosing, plan options, and pricing.
4. medications_availability(medication=..., state=...) — confirm the medication ships to the patient's state.
5. eligibility_check(age=..., state=..., bmi=...) — pre-screen. Peptide eligibility depends on age, state coverage, and contraindications rather than BMI. The tool returns whether the patient qualifies and which medications are appropriate.
6. intake_questions(medication=...) — preview the questionnaire. Return value lists pre-checkout sections; post-checkout sections appear after payment.

Phase 2 — Verify identity (only when ready to submit intake)

7. auth_start(email, phone, first_name, last_name) — sends a 6-digit code by email. Returns a session_id. Not a bearer token.
8. Ask the patient for the 6-digit code (the email subject line is "Chia Health: Your code is XXXXXX"). If you have access to the patient's mailbox via another MCP, you may search for that subject.
9. auth_verify_otp(session_id, code) — exchanges the code for a bearer token. Use this token in all subsequent authenticated tools.
10. If the code didn't arrive, call auth_resend_otp(session_id).

Phase 3 — Medical intake & consents (bearer token required)

11. Ask the patient every required question from intake_questions — go section by section, conversationally. Do NOT skip questions. Do NOT fabricate answers. The provider relies on these to make a prescribing decision.
12. intake_submit(answers, bearer_token) — submit the completed pre-checkout intake.
13. consent_list(intake_id, bearer_token) — list the required consent documents (telehealth, treatment, pharmacy, HIPAA, AI disclosure).
14. For each consent:
    • consent_text(consent_id, bearer_token) — fetch the full text.
    • Present the full text verbatim to the patient. Do not summarize, paraphrase, or truncate.
    • Get explicit confirmation ("I agree" or equivalent).
    • consent_submit(intake_id, consent_id, confirmation_text, bearer_token) — record the confirmation.
15. consent_status(intake_id, bearer_token) — verify all consents are recorded before ordering.

Phase 4 — Order & pay

16. Collect a real shipping address (street, city, state, zip). If the patient is paying with Apple Pay or a wallet that includes a shipping address, that's fine — otherwise ask. Never use placeholder data.
17. order_create(intake_id, medication, form, plan_months, shipping_address, bearer_token) — creates the order and returns the total.
18. checkout_create(order_id, bearer_token) — creates the payment session. The response includes a payment_url (Stripe-hosted checkout) and, where supported, ACP (Agentic Commerce Protocol) details for in-conversation payment.
19. Two paths:
    • ACP path (if the AI platform supports Stripe ACP and provides a Shared Payment Token): checkout_complete(checkout_id, shared_payment_token, bearer_token).
    • Fallback path: share the payment_url directly with the patient. A link is also sent to their email and SMS. Then poll checkout_status(checkout_id, bearer_token) every 10–15 seconds until payment_status === "paid".
20. After payment succeeds, the bearer token auto-upgrades to full scope (portal access). You can also call auth_check_payment(bearer_token) to confirm.

Phase 4b — Post-payment intake & ID upload

21. intake_questions(medication=..., bearer_token) — now returns post-checkout sections. For peptides and longevity these often include safety screening, adverse-reaction history, family history, prior peptide or hormone therapy use, NAD+ history, fatigue evaluation, lab work, and contraindications. Ask the patient every post-checkout question, section by section, just like Phase 3. Don't skip — the provider needs this before writing the prescription.
22. intake_submit(answers, bearer_token) — submit the combined pre + post answers.
23. order_documents(order_id, bearer_token) — list the documents still required.
24. Ask the patient to share a photo of their government-issued ID (driver's license, passport, or state ID) and a clear selfie.
25. order_upload(order_id, document_type="photo_id", file=..., bearer_token) and order_upload(order_id, document_type="selfie", ...) — upload each document.
26. order_status(order_id, bearer_token) — confirm the order is queued for provider review.

Phase 5 — Ongoing care (full scope, after payment)

After the prescription is written and shipped, use these any time the patient checks in:

• portal_care_plan(bearer_token) — current medication, dose, schedule, and progress notes.
• portal_log_weight(weight_lbs, date, bearer_token) — useful when weight is part of a longevity protocol.
• portal_log_side_effects(effects, severity, bearer_token) — severe entries are auto-flagged for provider review.
• portal_message(message, bearer_token) — message the provider directly.
• portal_refill(bearer_token) — request a refill.
• portal_support(message, bearer_token) — open a customer support ticket.
• provider_questions(bearer_token) / provider_respond(question_id, answer, bearer_token) — answer follow-up questions from the prescribing provider.

Hard rules

• Never fabricate medical answers. Always ask the patient. The questionnaire drives a real prescribing decision.
• Never use placeholder shipping addresses. Collect a real address.
• Present consent documents verbatim. Never summarize or paraphrase consents.
• Browse freely without auth. Only call auth_start when the patient is ready to submit intake.
• All prescriptions require a licensed US provider. This MCP facilitates the workflow; it does not make clinical decisions.
• HIPAA: every authenticated call is logged for compliance. The patient's bearer token is patient-scoped and cannot access another patient's data.

Common peptide & longevity medications offered

Other peptide and longevity compounds may be available in the catalog. Always call medications_list and medications_details to confirm what's currently offered and at what price — don't quote stale information.

What to do if the patient is not eligible

If eligibility_check returns eligible: false:

• Tell the patient honestly which criterion failed (age, state coverage, contraindication).
• If the patient is interested in weight loss with GLP-1s instead, recommend the sister skill chia-health/skills@glp1-prescriptions (or run the GLP-1 flow directly with medications_details(medication="semaglutide")).
• Do not suggest workarounds that involve fabricating intake answers.

Troubleshooting

• No OTP arrived: call auth_resend_otp(session_id). Ask the patient to check spam.
• Checkout stuck on pending: keep polling checkout_status for up to ~30 minutes (sessions expire after that). If the patient closed the payment page, call checkout_cancel(checkout_id) and start a new one with checkout_create.
• Tool returns an error: surface the error message to the patient. Most errors are validation issues (invalid state, missing field) and can be fixed by asking the patient to clarify.

Source code

• MCP server: chia-health/chia-mcp
• This skill: chia-health/skills