Skip to content
MCP server

splose MCP by usefulapi

Read splose patients, appointments, invoices, cases; book and cancel appointments…

Install
Runs
Remotely
Version
1.19.0
Listing updated
4 days ago

About splose MCP by usefulapi

splose MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.

Read splose patients, appointments, invoices, cases; book and cancel appointments, record payments.

Install

Run in a terminal

claude mcp add --transport http splose https://splose.usefulapi.io/mcp

Add to Settings → Connectors → Add custom connector

https://splose.usefulapi.io/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "splose": {
      "url": "https://splose.usefulapi.io/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "splose": {
      "type": "http",
      "url": "https://splose.usefulapi.io/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "splose": {
      "serverUrl": "https://splose.usefulapi.io/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "splose": {
      "type": "http",
      "url": "https://splose.usefulapi.io/mcp"
    }
  }
}

Tools this server provides (36)

Read directly from the server.

splose_get_account
The organisation and the practitioner who owns the API key, plus the key's expiry date. Good first call. GET /me.
splose_list_patients
Patients (clients) of the practice, filtered, in id order, as short rows: id, name, email, birthdate, phones, tags, alert, archived. Use splose_get_patient for the full record. HEALTH DATA: only look people up when the user asks. GET /patients.
splose_get_patient
One patient in full: contact details, address, NDIS number and plan info, Medicare/health fund, emergency contact, tags and custom fields. HEALTH DATA. GET /patients/{id}.
splose_list_appointments
Appointments in id order: start/end (UTC), service, location, practitioner, price, note and the per-patient status (Arrived, Did not arrive, Cancelled, Completed, cancellation reason, invoice id). Filter by time window, patient, practitioner or status. GET /appointments.
splose_get_appointment
One appointment in full, with each patient's status, case, invoice and cancellation details. GET /appointments/{id}.
splose_list_practitioners
Practitioners (staff): name, email, profession, role, active flag, online-booking flag, timezone and their location/service connections. GET /practitioners.
splose_get_practitioner
One practitioner in full, including provider numbers and connections. GET /practitioners/{id}.
splose_list_locations
Practice locations: title, address, phone, email, timezone, online-booking flag and the ids of the services offered there. GET /locations.
splose_get_location
One location in full. GET /locations/{id}.
splose_list_services
The service catalogue: name, type, code, duration (minutes), unit (Hour or Each), price, tax type, group size and tags. GET /services.
splose_get_service
One service in full, including provider-travel pricing. GET /services/{id}.
splose_list_contacts
Contacts (GPs, plan managers, referrers, invoice recipients): name, type, email, address, phones and the ids of their patients, invoices and cases. GET /contacts.
splose_get_contact
One contact in full. GET /contacts/{id}.
splose_list_cases
Cases (funding referrals and plans): case number, budget, hours or appointment allowance, issue and expiry dates, tracking type, open flag and utilisation alert. HEALTH/FUNDING DATA. GET /cases.
splose_get_case
One case in full, with its appointment connections. GET /cases/{id}.
splose_list_invoices
Invoices: number, issue/due dates, patient, contact, location, practitioner, subtotal, tax, total, paid amount, status (Draft, Awaiting Payment, Paid), line items and payment ids. Use status=Awaiting Payment for what is owed. GET /invoices.
splose_get_invoice
One invoice in full with its line items and payments. GET /invoices/{id}.
splose_list_payments
Payments received: payment number, amount, date, patient, location, payment method, the invoices each payment settles and credit allocations. GET /payments.
splose_get_payment
One payment in full. GET /payments/{id}.
splose_list_payment_methods
Payment methods (cash, card, bank transfer and so on) with their ids, needed to record a payment. GET /payment-methods.
splose_list_credit_notes
Credit notes: number, invoice, patient, subtotal, tax, total, sent status, items and allocations. GET /credit-notes.
splose_list_waitlist
Waitlist entries: patient, practitioner, location, wanted services, preferred days and time, tags and active flag. GET /waitlists.
splose_list_patient_forms
Forms sent to patients: title, status (Incomplete, In progress, Completed), patient, appointment, template and submission time. The form content is included. GET /patient-forms.
splose_list_support_activities
Non-appointment billable activities (NDIS support activities): patient, practitioner, service, item code, quantity, price, invoice id. GET /support-activities.
splose_list_busy_times
Blocked-out time in practitioner calendars (leave, admin time): start/end, location, practitioners, type and note. GET /busy-times.
splose_list_cancellation_reasons
Cancellation reasons with their ids, needed to cancel an appointment. GET /cancellation-reasons.
splose_list_custom_fields
The custom fields defined for patients: id, name, type (short text, dropdown, date and so on), required flag and options. GET /custom-field/.
splose_get_practitioner_availability
A practitioner's working-hours availability per date and location (start/end time, weekly or fortnightly repeat). The window is at most 100 days. This is the roster, not the open slots: use splose_find_free_slots for bookable times. GET /availabilities/{practitionerId}.
splose_find_free_slots
Bookable free slots for one or more practitioners at a location for one patient service, between from and to (the window is at most 7 days). Returns, per practitioner, the start/end of each open slot in UTC. Read-only. GET /free-slots.
splose_create_appointment
WRITE: books ONE appointment for one patient with one practitioner, service and location, from start to end (UTC). Splose may send the patient its normal booking confirmation or reminders according to the practice's settings, and the appointment can later be invoiced. Check splose_find_free_slots first. Not idempotent: calling twice books twice. POST /appointments.
splose_update_appointment
WRITE: changes the time, service, location, practitioner, case or patient of ONE existing appointment; send only the fields to change. Splose may notify the patient of a change according to the practice's settings. Same input twice gives the same result. PUT /appointments/{id}.
splose_cancel_appointment
WRITE: cancels ONE appointment with a cancellation reason (ids from splose_list_cancellation_reasons) and an optional note. The reason's billable rate may create a cancellation charge, and the patient may be notified per the practice's settings. For a group appointment pass patient_id to cancel only that patient's place; without it the whole appointment is cancelled. Cannot be undone through this
splose_mark_patient_arrived
WRITE: marks the patient of ONE appointment as arrived (check-in). For a group appointment pass patient_id to mark just that patient. Marking twice has the same effect. POST /appointments/{id}/arrival or /appointments/{id}/patients/{patientId}/arrival.
splose_create_patient
WRITE: adds ONE new patient record (first and last name required). Search with splose_list_patients first to avoid a duplicate. Patient messaging follows the practice's settings and communicationPreference. Not idempotent: calling twice creates two patients. HEALTH DATA: only enter what the user supplied. POST /patients.
splose_create_contact
WRITE: adds ONE contact (GP, plan manager, referrer, payer). type, name and email are required (type is Splose's contact type, e.g. Standard; see splose_list_contacts for the values in use). Not idempotent: calling twice creates two contacts. POST /contacts.
splose_record_payment
WRITE, MONEY: records ONE payment received (cash, card, transfer) against ONE invoice; it moves the invoice towards Paid and is shown in the patient's account. It does NOT charge anyone's card. amount must not exceed what is owed (check splose_get_invoice). Not idempotent: calling twice records two payments, and this server cannot delete a payment, so confirm the details with the user first and pa

splose MCP by usefulapi FAQ

How do I add splose MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http splose https://splose.usefulapi.io/mcp