A real demo, on data that was never real.
This demo runs on a composite family of four, generated synthetically — years of labs, medications, conditions, allergies, and visit notes that look and behave like the real thing but describe no actual person. Paste one URL into the AI you already use, and start asking.
There is nothing to set up first: no account, no sign-in, no card, nothing to agree to. The demo is its own server, separate from the one that reads real records — it has no accounts on it at all, so it cannot reach anyone's records, and no one can reach yours through it.
Signing up does not give you this family, and never will: a Thylib account holds your records and nothing else. Try the demo here, decide, then connect your own.
Paste one URL into your AI.
Any MCP-compatible client can add the demo connector. Below are the three most people use.
https://demo.thylib.com/mcp/emr_demo_1Nothing to set up first — no account, no sign-in, no card. This server holds only the synthetic family, and every tool on it is read-only.
- 1On claude.ai, open Settings → Connectors and click Add custom connector.
- 2Name it Thylib Demo and paste the URL above. Claude checks the server and will say it couldn't check the server — expected: it is looking for a sign-in, and this server has none. Click Continue anyway.
- 3Under Authentication choose No sign-in. Claude warns that anyone with the URL can use the connector — true, and the point: it is a public demo of a synthetic family, and no account exists on it. Leave Request headers empty and click Add.
- 4Start a new chat, open the + menu to enable Thylib Demo, and ask one of the questions below. Custom connectors work on every plan, including Claude Free (which allows one).
Custom connectors can only be added from claude.ai or the Claude desktop app — the Claude mobile app can't add them. But once you've added Thylib Demo from either of those, it syncs to your account and becomes available in the mobile app too.
These products rename menus often — if a step looks different, look for “custom connector,” “MCP server,” or “developer mode.” Any MCP-compatible client works with the URL above.
Four patients, four very different stories.
Each was generated with Synthea, an open-source synthetic-patient engine. Tap a question to copy it, then paste it into your AI.
Audie Altenwerth
68 · FType 2 diabetes that has slowly progressed into early kidney disease, with insulin and roughly 2,000 lab readings stretching back years — the kind of slow trend no single visit reveals.
José Emilio Zamora
55 · MMultimorbid: asthma, hypertension, and ischemic heart disease after a bypass — plus chronic pain and both drug and food allergies spread across many prescribers.
Lakesha Bauch
50 · FChronic intractable migraine and chronic pain alongside recurrent UTIs, obesity, and prediabetes — a tangle of overlapping conditions and medications.
Hildred Hill
5 · FA pediatric patient: childhood asthma and allergic rhinitis, a tree-nut allergy with an epinephrine auto-injector, and a full childhood immunization history.
Two people at once
A patient portal shows one person. Thylib holds the whole family, so a question can cross from one record into another. That matters because illness often runs in a family: the same condition in a parent and a child, an allergy two siblings share, a lab value drifting the same way in both. Seen together, one person's record can make sense of another's — a question worth asking at the next appointment, a risk worth watching earlier, a treatment that worked for one and might be worth discussing for the other.
A note on what these can find: Synthea generated the four independently, so no relationships, shared conditions, or inherited risks were designed into the set. The comparisons show what the tools can do across people; the resemblances a real family shows — the same diagnosis in a parent and a child, a pattern in the labs — are not here to be found.
The full clinical picture — read-only.
The demo exposes the same read-only tools as a real connection. It can look, summarize, and reason — it can never change a record.
When you're ready, the switch is clean.
The demo is a starting point, not a mode you have to unwind. Here's exactly what happens when you bring your own records in.
Two connectors, never one
The demo and your records are served by different servers. The demo one has no sign-in and reaches only synthetic records; the Thylib connector reaches only yours, and only after you sign in. Neither can see the other's data — that separation is how the software is built, not a setting, and it is why signing up will never show you this family.
Nothing synthetic lingers
Removing the demo connector in your AI's settings is the whole exit. Trying it never created a Thylib account, so there's no synthetic family sitting in the background of a later query — there was never an account to hold one.
Answers grounded in your records
Every real query is scoped to your own records and stamped with when they last synced, so the AI reasons over your actual history. Start a fresh chat when you switch — and because assistants now keep memory across chats, clear or pause that memory too, so nothing from the demo lingers.
A fresh chat clears the current conversation, but today's assistants also keep memory across chats — usually on by default. To be sure no demo detail follows you into your real records, explore the demo with memory off, or clear it when you switch:
Claude — Settings → Capabilities → Memory → View and manage to delete items, or Reset memory to wipe everything.
ChatGPT — explore the demo in a Temporary Chat (never uses memory), or clear it under Settings → Personalization → Manage memories.
Gemini — visit gemini.google.com/saved-info to delete entries or turn Memory off.
This is synthetic. Your records are richer.
When you connect your own MyChart, the AI reads across every provider you've seen — your real labs, medications, and history, kept private and yours to delete anytime.
Informational and educational only — not medical advice.