Splose
Manage patients, appointments, invoices and payments for health practices
Connects to Splose practice management software. Read patient records, appointments, invoices, cases and contacts. Book and cancel appointments, mark arrivals, record payments and create new patients and contacts.
Try asking Muse: "Show me my appointments for tomorrow and record a payment from a patient for their last invoice."
See the most upvoted connectors
Source: Found in the official MCP Registry (io.usefulapi/splose) · First listed October 29, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://splose.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
Splose is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://splose.usefulapi.io/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 182ms. Worked in n/a of checks over 30 days.
Screening · October 29, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 36
splose_get_accountThe organisation and the practitioner who owns the API key, plus the key's expiry date. Good first call. GET /me.splose_list_patientsPatients (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_patientOne 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_appointmentsAppointments 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_appointmentOne appointment in full, with each patient's status, case, invoice and cancellation details. GET /appointments/{id}.splose_list_practitionersPractitioners (staff): name, email, profession, role, active flag, online-booking flag, timezone and their location/service connections. GET /practitioners.splose_get_practitionerOne practitioner in full, including provider numbers and connections. GET /practitioners/{id}.splose_list_locationsPractice locations: title, address, phone, email, timezone, online-booking flag and the ids of the services offered there. GET /locations.splose_get_locationOne location in full. GET /locations/{id}.splose_list_servicesThe service catalogue: name, type, code, duration (minutes), unit (Hour or Each), price, tax type, group size and tags. GET /services.splose_get_serviceOne service in full, including provider-travel pricing. GET /services/{id}.splose_list_contactsContacts (GPs, plan managers, referrers, invoice recipients): name, type, email, address, phones and the ids of their patients, invoices and cases. GET /contacts.splose_get_contactOne contact in full. GET /contacts/{id}.splose_list_casesCases (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_caseOne case in full, with its appointment connections. GET /cases/{id}.splose_list_invoicesInvoices: 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_invoiceOne invoice in full with its line items and payments. GET /invoices/{id}.splose_list_paymentsPayments received: payment number, amount, date, patient, location, payment method, the invoices each payment settles and credit allocations. GET /payments.splose_get_paymentOne payment in full. GET /payments/{id}.splose_list_payment_methodsPayment methods (cash, card, bank transfer and so on) with their ids, needed to record a payment. GET /payment-methods.splose_list_credit_notesCredit notes: number, invoice, patient, subtotal, tax, total, sent status, items and allocations. GET /credit-notes.splose_list_waitlistWaitlist entries: patient, practitioner, location, wanted services, preferred days and time, tags and active flag. GET /waitlists.splose_list_patient_formsForms 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_activitiesNon-appointment billable activities (NDIS support activities): patient, practitioner, service, item code, quantity, price, invoice id. GET /support-activities.splose_list_busy_timesBlocked-out time in practitioner calendars (leave, admin time): start/end, location, practitioners, type and note. GET /busy-times.splose_list_cancellation_reasonsCancellation reasons with their ids, needed to cancel an appointment. GET /cancellation-reasons.splose_list_custom_fieldsThe 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_availabilityA 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_slotsBookable 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_appointmentWRITE: 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 splossplose_update_appointmentWRITE: 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_appointmentWRITE: 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 patiesplose_mark_patient_arrivedWRITE: 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_patientWRITE: 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 entsplose_create_contactWRITE: 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_paymentWRITE, 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: callinLink
https://splose.usefulapi.io/mcpQuestions about Splose in Muse
How do I connect Splose to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Splose to help me. It is a free service with an MCP server at https://splose.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is Splose working right now?
At the last check (October 29, 2026, 23:01 UTC) the endpoint was working, answering in 182ms. It is checked every 15 minutes.
Is Splose safe to connect to Muse?
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can Splose do in Muse?
It exposes 36 tools, including splose_get_account, splose_list_patients, splose_get_patient, splose_list_appointments. For example, you could ask Muse: "Show me my appointments for tomorrow and record a payment from a patient for their last invoice."
Follow Splose
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/splose)). If you build Splose, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/splose"><img src="https://musedirectory.ai/badge/splose.svg" alt="Splose on musedirectory.ai" width="236" height="40"></a>