WaiRequest a demo

The Clinicians MCP server

Updated 16 November 2026.

What it is for

The Clinicians MCP server lets an AI assistant such as Claude work in a clinician’s own Wai account. The assistant can read the clinician’s worklist, patients and clinical admin, and it can prepare work for the clinician to finish. Each clinic has its own server, at its own address, in the clinic’s own region.

How to connect

  1. Ask your clinic for its server address. It ends in /api/v1/mcp.
  2. Add the address as a custom connector in your assistant.
  3. Sign in with your own clinic account when the assistant asks. The assistant finds the sign-in page from the server itself, through OAuth 2.1 with PKCE.
  4. Approve the access the assistant asks for. You can withdraw it at any time, and the assistant is refused from its next request.

The token your assistant receives works on your clinic’s server and nowhere else. It is bound to that server’s address, so it is refused by another clinic and by every other Wai server.

What a connected assistant can do

  • Reads run when the assistant calls them, and they change nothing.
  • Tools that add something of your own, such as a task or a draft, run when the assistant calls them. They never change a patient’s record.
  • Changes to a patient’s record are not offered to a connected assistant. You make them in the app, where each one waits for your approval.
  • A connected assistant can ask you to sign a document. Only you can sign it.

How signing works

When an assistant asks for a signature, it receives a link for each document and nothing is signed. You open the link on your own device. The page shows the document, the patient’s name with a second identifier, and which assistant asked. You sign with Face ID or a passkey, and the signature is checked against the exact version the assistant asked about.

The assistant then asks the server whether the document is signed. If the document changed after it asked, it is not reported as signed, and the assistant is given a new link for the version that is there now.

Only the clinician whose consultation it is can sign. A patient with no date of birth or record number on file cannot be signed for until one is added. Prescriptions are signed in SignatureRX when they are issued, not here.

What is recorded

Each call is recorded once, with the tool, what happened and who made it. The record holds neither the call’s details nor its answer, so it never becomes a second copy of the patient’s record. Each signature is recorded with the clinician, the assistant that asked and the passkey that was used.

A connected assistant can read your own record back to you, by day if you ask for one. It shows your calls, the calls that were refused and your signatures, and never another clinician’s.

Where it runs

Each clinic’s server runs in one region, the UK, the EU, Germany, the Gulf or the US. A token issued for one clinic or region is refused at every other, and a patient, visit or document from another clinic is refused before any tool runs.

For developers

The server speaks the Model Context Protocol, version 2026-07-28, and answers older clients in their own version. It describes itself in a Server Card at /api/v1/mcp/server-card on the clinic’s address, and /.well-known/ai-catalog.json on the same address links to it. The card gives the OAuth audience, the region, and how many tools sit in each tier and each toolset. It names no clinic and no tool, and the tools themselves come from tools/list once the assistant is signed in. A clinician’s own record is offered as read-only resources from resources/list, with a template for one day. A client that declares the tasks extension is given evidence and chart questions as tasks, and polls tasks/get for the answer.

For anything else, write to team@wellnessa-i.com.