MCP (Model Context Protocol) server for the **[Chia Health](https://chia.health)** telehealth prescription platform. Enables AI assistants (ChatGPT
Chia MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Chia MCP directly instead of describing what you should do. MCP (Model Context Protocol) server for the Chia Health telehealth prescription platform. Enables AI assistants (ChatGPT, Claude, Gemini, OpenClaw, Copilot, and custom agents) to help patients browse medications.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Chia MCP is connected, these are the calls the assistant has available:
Transport — ** Streamable HTTPACP — checkout.complete accepts a Shared Payment Token (SPT) from the AI platform and confirms the PaymentIntent. Instant, in-conversation paymentFallback — The agent shares the payment_url (authenticated magic-link) with the patient. The patient opens it in their browser, auto-authenticates, and pays onOTP — First Auth** — Email ownership verified via 6-digit OTP before any patient data access. SHA-256 hashed tokens with scoped access (guest/full). NoIssues — ** github.com/chia-health/chia-mcp/issuesWebsite — ** chia.healthEmail — ** engineering@chia.healthCategory — Toolsauth.start — Noauth.verify_otp — Noauth.resend_otp — Noauth.check_payment — GuestAmong the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Chia MCP's toolset — Transport, ACP, Fallback and 11 more — is a fair guide to whether it matches your workflow. It is maintained by chia-health; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Transport | ** Streamable HTTP |
| 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 (authenticated magic-link) with the patient. The patient opens it in their browser, auto-authenticates, and pays on the Chia Health checkout page. The agent polls auth.check_payment to de |
| OTP | First Auth** — Email ownership verified via 6-digit OTP before any patient data access. SHA-256 hashed tokens with scoped access (guest/full). No token issued without email verification. |
| Issues | ** [github.com/chia-health/chia-mcp/issues](https://github.com/chia-health/chia-mcp/issues) |
| Website | ** [chia.health](https://chia.health) |
| ** engineering@chia.health | |
| Category | Tools |
| auth.start | No |
| auth.verify_otp | No |
| auth.resend_otp | No |
| auth.check_payment | Guest |
| medications.list | List all medications with categories, forms, and pricing |
| medications.details | Detailed info for a specific medication (plans, pricing, what's included) |
{
"mcpServers": {
"chia-health": {
"url": "https://mcp.chia.health/"
}
}
}Configuration as documented by the project. Restart the client after saving.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.