ReferralMD – Model Context Protocol

Your referral network,
answerable in plain language.

Finding a cardiologist near Evanston who takes new patients and has a Thursday opening means a provider search, a filter panel, several profiles and a scheduling grid — and doing it again when the first three are full. It’s the same question every time. Ask it once instead, in the assistant your team already has open.

Someone Asks

“Who can see a cardiology patient near Chicago in the next two weeks?”

The Assistant Calls One Tool

provider_lookup —
action: search
specialty: cardiology
accepting: true
state: IL

Your Directory Answers

Your Directory Answers

Sarah Williams, MD Chicago
Priya Raman, MD Evanston
Elena Vasquez, DO Milwaukee

Then: earliest opening, full record, phone.

The answer, not another screen of search results.

Your coordinators already know what they need. What costs them the afternoon is the traversal — filtering, opening profiles, checking calendars, starting over. The assistant does the traversal and comes back with names and times.

What The Coordinator Does

Ask Once

No filter panels, no profile-by-profile checking, no switching to the scheduling grid.

 
Credentials Stored

None

Standard sign-in, the same kind you already use elsewhere. No API keys and no shared passwords to circulate, store or rotate.

Write Access

Zero

Every exposed action is read-only and annotated as such, so clients can shjow it as safe.

Time to Connect

One consent

Approve once in a browser. Tokens refresh themselves from then on.

A referral coordinator’s afternoon, in three questions.

Nothing new to learn and nothing new to log into. The assistant chooses the filters, follows up on its own answer, and cites real records from your directory — so the coordinator reads names and times instead of navigating to them.

  1. “Find cardiologists in Illinois taking new patients.”
    search · specialty + accepting + state
  2. “Which of them has the earliest opening?”
    check_availability · 14-day window, open slots only
  3. “Give me her full record and a verified phone number.”
    get · NPI, specialties, locations, verified contacts

Built for a system that holds patient data.

Clinical directories aren’t a public search index. The integration respects that at every layer.

Scoped to your organization

Tenacity – search returns providers in your own own organization and the contacts you’ve added. never a platform-wide directory.

Access that only works here

Containment – signing in to ReferralMD grants access to ReferralMD and nothing else. It cannont be turnes around and used against another system.

A human approves once

Consent– authorization happens in a browser, ot of band. The server never prompts mid request and never holds your password.

Every name comes from your directory

Accuracy – the assistant can only report what the API returned. It cannot invent a provider, a phone number, or any opening. And, if a filter isn’t supported, the request is refused rather than ignored.

What it means day to day

  • Nothing to install. Your team keeps using the assistant they already have.
  • Sign in once. Access renews quietly — nobody re-authorizes every hour.
  • Remove someone in ReferralMD and their assistant access ends at the same moment.
  • It can look things up and nothing else — no edits, no deletions, no exceptions.
  • Your directory stays in ReferralMD. Nothing is copied out or kept elsewhere.
  • Answers cite real records, so anything on screen can be checked in the app.

Evaluating the security model, or connecting it yourself? The integration guide covers authentication, tenancy and the full API surface.

See it answer a real question.

Add the endpoint to the assistant your team already uses, sign in once, and ask. The integration guide walks through it in five minutes.

Read the Integration Guide
Schedule a Demo