Chia Health MCP Server
Integrate licensed US telehealth flows—GLP-1 intake, consents, and Stripe ACP—into health products via a HIPAA-oriented MCP with 30 tools.
Overview
health.chia/chia-mcp is an MCP server for the Build phase that provides 30 HIPAA-oriented US telehealth tools including GLP-1 intake, consents, and Stripe ACP over streamable HTTP.
What is this MCP server?
- 30 MCP tools for telehealth intake, consents, and medication workflows
- Licensed US telehealth positioning with HIPAA-compliant framing
- GLP-1 medication pathway called out in server description
- Stripe ACP (Automated Checkout Protocol) integration surface
- Streamable-http remote at https://mcp.chia.health/
- HIPAA-compliant positioning per server description
- GLP-1 medications and Stripe ACP called out
Community signal: 5 GitHub stars.
What problem does it solve?
You are building a health product and need programmatic telehealth and checkout steps without stitching together every clinical and payment integration manually.
Who is it for?
Experienced solo builders shipping US telehealth or GLP-1-adjacent SaaS who already plan legal, HIPAA, and clinical oversight alongside MCP automation.
Skip if: Hobby projects outside licensed telehealth, non-US-only products without Chia coverage, or teams uncomfortable with regulated health and payment data flows.
What do I get? / Deliverables
After connecting https://mcp.chia.health/, your agent can invoke Chia’s 30 tools for intake, consents, and Stripe ACP-aware flows under your compliance guardrails.
- 30-tool telehealth MCP integration in your agent stack
- Structured intake and consent flows callable from MCP
- Remote MCP registration pointing at mcp.chia.health
Recommended MCP Servers
Journey fit
Telehealth and payment-ready patient flows are built when you wire regulated third-party services into your product backend and agent tooling. Chia exposes clinical and commerce primitives as MCP tools, which is classic build-phase external service integration.
How it compares
Regulated telehealth integration MCP with 30 tools, not a generic code-review or SEO skill.
Common Questions / FAQ
Who is health.chia/chia-mcp for?
Developers building HIPAA-conscious US telehealth experiences who want MCP-accessible intake, consent, GLP-1, and Stripe ACP operations via Chia Health.
When should I use health.chia/chia-mcp?
Use it during build integrations after you have validated a telehealth offering and need agent-callable Chia workflows rather than one-off REST experiments.
How do I add health.chia/chia-mcp to my agent?
Add the streamable-http remote MCP URL https://mcp.chia.health/ in your MCP client configuration and follow Chia Health onboarding for any account, clinical, and Stripe requirements beyond the public manifest.