Chia Health Mcp
@chia-health
Chia Health MCP Server — Patient workflow integration for a licensed US telehealth platform. Browse GLP-1 medications (semaglutide, tirzepatide), peptide therapies (sermorelin, NAD+, glutathione), and longevity treatments. Check eligibility, complete intake, sign consents, and ma
概要
What is Chia Health MCP?
Chia Health MCP is a remote Model Context Protocol server for the Chia Health telehealth prescription platform. It enables AI assistants (ChatGPT, Claude, Gemini, Copilot, and custom agents) to help patients browse medications, complete medical intake, sign consent documents, place orders, pay via Stripe ACP, and manage treatment through natural conversation. Prescriptions are evaluated by licensed US healthcare providers and filled by FDA-regulated 503A compounding pharmacies across all 50 US states + DC.
How to use Chia Health MCP?
Chia Health MCP is a remote server with Streamable HTTP transport — no local installation required. Configure your MCP client to connect to the server URL https://mcp.chia.health/. Configuration examples are provided for Claude Desktop, Cursor, Cline/VS Code, and Windsurf. After connecting, the AI assistant can call tools such as doctormcp_list_medications, doctormcp_check_availability, and doctormcp_get_intake_questions immediately (public tools) or after obtaining a bearer token (patient-specific tools).
Key features of Chia Health MCP
- 30 tools across Discovery, Qualification, Consent, Ordering, Checkout, Patient Portal, and Provider categories.
- Public discovery tools require no authentication; patient-specific tools require a bearer token.
- HIPAA compliant: audit logging, immutable consent records, input sanitization, bearer token auth, and rate limiting.
- Stripe ACP integration with both in‑conversation payment (Shared Payment Token) and fallback payment URL.
- Full ordering flow: intake questionnaire, consent documents, order creation, checkout, and payment.
Use cases of Chia Health MCP
- Discovery and eligibility — AI browses medication categories, checks pricing, availability by state, and pre‑screens patient eligibility.
- Full ordering workflow — Patient completes intake, signs all required consents, creates an order, and pays via Stripe ACP or a payment link — all through conversation.
- Patient portal actions — Log weight, report side effects, message the provider, request a refill, or contact support.
- Provider communication — Answer follow‑up questions from the healthcare provider via the AI.
FAQ from Chia Health MCP
What transport does Chia Health MCP use?
The server uses Streamable HTTP transport. The server URL is https://mcp.chia.health/.
Do I need to install anything locally?
No. Chia Health MCP is a remote server — you only need to configure your MCP client to connect to the server URL.
Is authentication required to use the tools?
Some tools (Discovery: list medications, check availability, eligibility) are public and require no authentication. All patient‑specific tools (intake, consent, ordering, checkout, patient portal) require a bearer token obtained during the intake flow.
How are prescriptions handled?
All prescriptions are evaluated and approved by licensed US healthcare providers. Chia Health MCP facilitates the patient workflow — it does not make clinical decisions.
What is Stripe ACP and how does payment work?
Chia Health MCP uses Stripe’s Agentic Commerce Protocol (ACP). Payment can be completed in‑conversation using a Shared Payment Token, or via a fallback Stripe‑hosted payment URL. Checkout sessions expire after 30 minutes.
