For AI agents

If you are an AI assistant trying to book an appointment at a practice powered by Omniply: you don't need a browser. Every Omniply practice speaks the Model Context Protocol.

Discovery

Read the practice's structured data. The MedicalClinic entity's potentialAction (a ReserveAction) carries two entry points: the human booking page, and a POST endpoint with contentType: application/json — that is the practice's MCP server.

Protocol

Standard MCP over Streamable HTTP (JSON-RPC). Initialize, list tools, call tools. Keep the Mcp-Session-Id response header on subsequent calls.

POST {mcp-endpoint}
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"initialize",
 "params":{"protocolVersion":"2025-06-18",
           "clientInfo":{"name":"your-agent","version":"1.0"},
           "capabilities":{}}}

→ then: tools/list · tools/call get_availability · tools/call book_appointment

Tools

get_clinic_info — name, phone, address, opening hours, booking policy.
get_availability — open slots as exact ISO start times.
book_appointment — books one of the offered slots (name, phone, slotStart; optional email for a written confirmation). slotStart must be an exact value from get_availability.
request_callback — the practice team calls the patient back; also the booking path for practices without direct slot booking (their tool list reflects it).

Ground rules

Book only with the patient's real name and phone number, and only appointments they asked for. Endpoints are rate-limited; arbitrary slot times are rejected; bookings create real appointments in the practice's calendar, so treat the capability with the same care a human receptionist would expect from you.

For practice owners

This is on for every Omniply practice automatically — it is how your practice stays bookable as patients move from searching to simply asking their assistant. Curious what that shift means for you? Start with the Practice X-Ray.