Integration

HearLink integration

HearLink is a UK practice management system and CRM for audiology and hearing care clinics. An agent can find, read, create and update patient records, list, read, book, reschedule, cancel and delete appointments, check bookable slots, list clinics, appointment types and bookable clinicians, read the online booking configuration, take an online booking that matches or creates the patient, and read invoices. Patient, appointment and invoice tools handle personal and health data. Webhook subscriptions are made in the HearLink portal, not through the API. Authentication is an API key generated in the HearLink account, sent in the x-api-key header; each key acts with its user's permissions.

Connect HearLink How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in HearLink.Built from the 16 HearLink tools below, on the connection you add once.

What you can do with HearLink

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Appointment, 4 operations

delete_appointmentDelete appointmentDELETEAgents: ask firstPermanently deletes an appointment, cancels its scheduled reminders and automations, and frees the slot for online booking. Cannot be undone; to keep a record, set cancelled with update_appointment instead.
get_appointmentGet appointmentGETAgents: ask firstReturns one appointment by UID: type, clinic, clinician, start and end, patient reference, notes, outcome and status flags. Contains personal data.
list_appointmentsList appointmentsGETAgents: ask firstLists appointments whose start falls between from and to (YYYY-MM-DD, at most 92 days, organisation timezone), sorted by start, with optional clinic, type, clinician or patient filters. Returns patient names (personal data).
update_appointmentUpdate appointmentPATCHAgents: ask firstChanges an appointment: send only the fields to change. Any of appointmentTypeId, clinicId, assigneeId, date, start, end or location reschedules it and re-checks availability; the status flags are applied directly.

Create, 3 operations

create_appointmentCreate appointmentPOSTAgents: ask firstBooks an appointment for an existing patient (writes to the clinic diary). The type, clinic, clinician and slot must exist and be free; sendConfirmation true also emails or texts the patient.
create_online_bookingCreate online bookingPOSTAgents: ask firstBooks a slot for a person in one call: matches them to an existing patient (name, phone, email, birth date, address) or creates a new patient, then creates the appointment. sendConfirmation decides if HearLink messages them.
create_patientCreate patientPOSTAgents: ask firstCreates a patient record (personal data). Give fullName, primaryPhoneNumber, tracking, and exactly one of each pair: referralId or referralName, primaryClinicId or primaryClinicName, statusId or statusName.

Patient, 3 operations

get_patientGet patientGETAgents: ask firstReturns one patient record by UID: contact details, date of birth, address, GP, emergency contact, status, clinic, last test and fitting dates, custom fields. Personal and health data.
list_patientsList patientsGETAgents: ask firstLists patients (newest first, paginated), or searches them: pass exactly one of query, phoneNumber or emailAddress (up to 50 results, dob narrows), or externalSystemId alone. Returns personal and health data.
update_patientUpdate patientPATCHAgents: ask firstUpdates a patient record: only the fields sent change, omitted fields keep their current values. Send at least one field. Returns the updated patient record (personal and health data).

Appointment type, 1 operation

list_appointment_typesList appointment typesGETAgents: ask firstLists every appointment type of the organisation (uid, name, duration in minutes), internal ones included, sorted by name; paginated with cursor. Needs the appointment_types:browse permission.

Availability, 1 operation

list_availabilityList availabilityGETAgents: ask firstReturns bookable slots (date, start time, free clinicians) for one appointment type at one clinic between from and to (YYYY-MM-DD, from today, at most 62 days). Dates with no slot are left out.

Clinic, 1 operation

list_clinicsList clinicsGETAgents: ask firstLists the organisation's clinics (uid, name, address with coordinates, email, phone, appointment types disabled there), sorted by name; paginated with cursor. Any active API key may call it.

Config, 1 operation

get_online_booking_configGet online booking configGETAgents: ask firstReturns what can be booked online: the bookable clinics (weekdays, advance window), appointment types (duration, price, requiresPayment), clinicians, the patient fields the organisation requires, and its timezone.

Invoice, 1 operation

get_invoiceGet invoiceGETAgents: ask firstReturns one invoice by UID: number, dates, status, patient, audiologist, line items, discount, VAT, subtotal and total, linked appointment and Xero id. Contains personal data.

Staff, 1 operation

list_staffList staffGETAgents: ask firstLists the clinicians who can hold appointments (uid and name only), sorted by name; paginated with cursor. Needs users:read, appointments:read:my_clinics or appointments:read:all.

Use HearLink from Claude Code, Cursor or Codex

Connect HearLink in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its HearLink operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect HearLink

Create your workspace
Sign up free. Nothing to install.
Connect HearLink once
Add your HearLink connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.