auth_startLABSCO 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 throughintake_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_completetakes a Stripe Shared Payment Token in-conversation,checkout_createreturns 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, named doctormcp, 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
Paste a URL — add the endpoint to your client
USE CASES
01
Answering 'can I get this where I live, and what does it cost'
Check shipping to a state and read the plan pricing before asking the patient for anything at all.
02
Screening someone out before they fill in a questionnaire
Test age, state and BMI first, so an ineligible patient does not spend twenty minutes on an intake.
03
Running the intake conversationally
Pull the structured questionnaire, ask it a question at a time in plain language, and submit the answers for provider review.
04
Taking payment without leaving the chat
Create the order, then either confirm with a shared payment token or hand over a link and poll until it clears.
05
Checking in on treatment weeks later
Log a weight, report a side effect, and message the provider from the same thread.
34 tools
Listed in project docs. Your client may show a different list.
auth_verify_otpauth_resend_otpauth_check_paymentmedications_listmedications_detailsmedications_availabilitymedications_pricingmedications_categorieseligibility_checkintake_questionsintake_submitintake_statusconsent_listconsent_textconsent_submitconsent_statusorder_createorder_statusorder_documentsorder_uploadcheckout_createcheckout_updatecheckout_completecheckout_statuscheckout_cancelportal_log_weightportal_log_side_effectsportal_messageportal_care_planportal_refillportal_supportprovider_questionsprovider_respondBEFORE YOU INSTALL
What to know first
Tools you get
34 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://mcp.chia.health/MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"chia-health": {
"url": "https://mcp.chia.health/"
}
}
}Cline
CLINE · JSON
{
"mcpServers": {
"chia-health": {
"type": "streamableHttp",
"url": "https://mcp.chia.health/"
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"chia-health": {
"serverUrl": "https://mcp.chia.health/"
}
}
}
