Read splose patients, appointments, invoices, cases; book and cancel appointments, record payments. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"splose": {
"url": "https://splose.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"splose": {
"type": "http",
"url": "https://splose.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Splose API key and Region.
The workspace owner requests API access from splose Support (paid plans only), then creates the key in splose under My account, API. The key acts with the permissions of the user who owns it. Pick the region your splose account is hosted in (Australia, or the UK for api-uk.splose.com). Patient records are health data: your key is used only to call the Splose API on your behalf and is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Splose API key and Region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the splose connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
splose_get_account | read | Get the account behind the API key The organisation and the practitioner who owns the API key, plus the key's expiry date. Good first call. GET /me. |
splose_list_patients | read | 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 | read | Get a 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 | read | 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 | read | Get an appointment One appointment in full, with each patient's status, case, invoice and cancellation details. GET /appointments/{id}. |
splose_list_practitioners | read | List practitioners Practitioners (staff): name, email, profession, role, active flag, online-booking flag, timezone and their location/service connections. GET /practitioners. |
splose_get_practitioner | read | Get a practitioner One practitioner in full, including provider numbers and connections. GET /practitioners/{id}. |
splose_list_locations | read | 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 | read | Get a location One location in full. GET /locations/{id}. |
splose_list_services | read | 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 | read | Get a service One service in full, including provider-travel pricing. GET /services/{id}. |
splose_list_contacts | read | 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 | read | Get a contact One contact in full. GET /contacts/{id}. |
splose_list_cases | read | 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 | read | Get a case One case in full, with its appointment connections. GET /cases/{id}. |
splose_list_invoices | read | 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 | read | Get an invoice One invoice in full with its line items and payments. GET /invoices/{id}. |
splose_list_payments | read | 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 | read | Get a payment One payment in full. GET /payments/{id}. |
splose_list_payment_methods | read | 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 | read | List credit notes Credit notes: number, invoice, patient, subtotal, tax, total, sent status, items and allocations. GET /credit-notes. |
splose_list_waitlist | read | List waitlist items Waitlist entries: patient, practitioner, location, wanted services, preferred days and time, tags and active flag. GET /waitlists. |
splose_list_patient_forms | read | 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 | read | 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 | read | 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 | read | List cancellation reasons Cancellation reasons with their ids, needed to cancel an appointment. GET /cancellation-reasons. |
splose_list_custom_fields | read | List patient 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 | read | Get a practitioner's 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 | read | Find free appointment 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 | Create an 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 | Update (reschedule) an 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 | Cancel an 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 server: confirm with the user first and pass confirm: true. POST /appointments/{id}/cancellation or /appointments/{id}/patients/{patientId}/cancellation. |
splose_mark_patient_arrived | write | Mark a patient as 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 | Create a 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 | Create a 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 | Record a payment against an invoice 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 pass confirm: true. Ids come from splose_get_invoice and splose_list_payment_methods. POST /payments. |
splose_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
splose_request_feature | Request a missing feature Tell usefulapi that the user needs something the Splose tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
splose_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Splose (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
splose_cancel_subscription | Cancel the Pro subscription Cancel the caller's Splose Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run splose_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this splose server only. Subscribe with splose_upgrade (it returns a Stripe Checkout link). Cancel any time with splose_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running splose_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by splose. The server calls the splose API with your own splose access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Splose API key and Region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Splose API key and Region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the splose API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in splose.
Yes, if you approve it. 7 of the 36 splose tools can create or change data. The other 29 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this splose server only. Cancel any time: Pro then runs to the end of the paid period. Run splose_usage_status to see how many calls you used.
Ask the AI to run splose_upgrade: it returns a Stripe Checkout link. To cancel, run splose_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with splose_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.