Yes: you can connect Claude straight to your EHR, as long as the EHR runs an MCP server, the open standard AI assistants use to plug into outside tools. Eureka does, in production, today. This page is the short version: get an API key, add the connection in Claude Code or Claude Desktop, and start asking Claude about your own schedule, your patients, and your billing.
What you need
| You need | Detail |
|---|---|
| A Eureka account | An active practice on eureka.md. |
| An API key | Per doctor, scoped to your practice only. Ask in your practice Slack channel or at eureka.md/support. |
| Claude Code or Claude Desktop | Either works. Claude Code runs in a terminal; Claude Desktop and claude.ai are a normal app or browser tab. Use whichever you already have open most days. |
Your key is a long string starting with eur_. Treat it like a password: it opens read and write access to your own patient data, nobody else's. We store keys hashed, track when each one was last used, and can revoke one on request if it ever leaks.
How do you connect Claude to Eureka?
Claude Code
Run one command in your terminal, swapping in your own key:
claude mcp add --transport http eureka https://api.eureka.md/mcp --header "Authorization: Bearer eur_YOUR_KEY_HERE"
That's the whole setup. Ask Claude "what tools do you have from eureka" to confirm the connection worked, or run /mcp inside Claude Code to see it listed alongside anything else you've connected.
Claude Desktop or claude.ai
- Go to Settings, then Connectors, then Add custom connector.
- Enter the server URL:
https://api.eureka.md/mcp. - Open Request headers and add one: name
Authorization, valueBearer eur_YOUR_KEY_HERE, marked Required. - Click Add, then turn the connector on for your chat from the "+" menu.
Request headers on custom connectors are a beta option Anthropic is still rolling out, so you may not see that section yet. If it's missing, mcp-remote is the workaround: it runs locally, attaches your header, and forwards the connection to Eureka. That's a local MCP server entry in Claude Desktop, not the custom-connector URL field, roughly npx mcp-remote https://api.eureka.md/mcp --header "Authorization: Bearer eur_YOUR_KEY_HERE" in your config. Check the mcp-remote project's own docs for the exact syntax before you rely on it. Either route ends the same place, with Claude holding a live connection to your practice.
For the full tool list, the resource types, and the prompts that ship with the server, see the MCP server docs.
What do you ask it, once it's connected?
The honest answer: whatever you'd ask an office manager who could also read a chart. A few examples doctors actually use:
| You ask | What happens |
|---|---|
| "Prep my Thursday" | Runs the built-in morning brief: your schedule, chart context, and anything that needs attention before you walk in. |
| "Book Mrs. K a 30-minute follow-up next Tuesday afternoon" | Checks your open slots and schedules it. By default the visit is left unpaid and the patient is not messaged, unless you say otherwise. |
| "Draft a reply to Mr. R about rescheduling his Tuesday visit" | Drafts the message from his chart and appointment history. You review it and send it yourself. |
| "Which patients haven't booked a follow-up 90 days after their last visit?" | Checks your patient list against appointment history and flags the gap. |
| "Pull my July collections and flag unpaid visits" | Reads billing records for the month and lists what's still outstanding. |
| "Summarize Jane Doe's chart before her 2pm" | Pulls her chart and visit timeline into a summary. |
| "Start a note for my 3pm and bring in her intake form answers" | Opens the note and drops in what she wrote at intake. |
| "Order a lipid panel for [patient] ahead of her follow-up" | Creates the lab order as pending. You authorize it before it goes anywhere. |
| "What does next week look like, and where are the open slots?" | Reads your schedule and availability. |
| "Which patients are sitting on the recall list for missed follow-ups?" | Reads the recall queue. |
| "Turn today's visit note into a handoff summary" | Runs the note through finalize and into a handoff in one pass. |
You don't need to learn special phrasing for any of this. Claude picks the right tool from a plain request, the same way it would if you asked a person.
What can't Claude do through Eureka?
| It can't | Why |
|---|---|
| Touch a patient's card while scheduling | New bookings default to leave-unpaid. A card hold happens only when you explicitly ask for one, and patients aren't messaged about a booking unless you say so. |
| Sign a note | Signing is yours. Claude can draft and revise a note; it can't put your name on it. |
| Send a prescription | e-Rx is not exposed through the MCP order tools at all; prescribing stays in the app. Refill requests can arrive as one-click proposals from our Slack assistant, and you approve each one. |
Approvals stay with you. Claude can read almost everything in your practice and draft almost anything you ask for. It cannot finalize a clinical decision on its own.
Is this HIPAA compliant?
Eureka signs a business associate agreement with your practice, which covers how Eureka itself handles your patient data. Connecting your own Claude account is a separate question: your practice is the covered entity, and you're responsible for having the right agreement with Anthropic in place before you send PHI through it. Most consumer Claude subscriptions don't include a BAA. Anthropic launched Claude for Healthcare in January 2026, and some vendors, Anthropic included, offer BAAs on enterprise or API tiers, so check your own plan's BAA status with Anthropic directly before you connect anything with real patient data in it. If you want a lower-risk starting point, allow only the read tools in your client: every write tool ends in _action, so a single deny pattern in Claude Code's permission settings blocks all of them. That gives you a Claude that can look up almost anything but change nothing, until you're ready to extend it. None of this is legal advice, just the practical shape of who's responsible for what.
For the broader case on why a doctor would want this kind of access in the first place, see Claude for doctors. Using ChatGPT instead of Claude is a different setup: see connecting ChatGPT to Eureka. More setup and troubleshooting questions are answered in the FAQ.
Need an API key? Ask in your practice Slack channel, or reach out at eureka.md/support.