Report whether this server holds a Client Portal session, for which practice, and how that practice was determined (from a sign-in link, from SIMPLEPRACTICE_PRACTICE, or remembered from the stored session). Reads local state only — makes no network call.

Ask SimplePractice to email a sign-in link to a Client Portal address. The portal has no password — this is how you sign in. Sends a real email and is rate-limited per email address AND per IP, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). A success does not prove the address has an account: the API answers identically for unknown addresses by design.

Exchange an emailed sign-in link (or the token in it) for a Client Portal session. Accepts the whole link or just the part after the "#". Prefer passing the WHOLE link: its address names the practice, so no practice has to be configured, and this server remembers it afterwards. Tokens are single-use and last 24 hours.

Exchange a 6-digit Client Portal sign-in PIN for a session, for practices that email a code instead of a link. Single-use.

Discard the stored Client Portal session from local state.

The practice, the signed-in client, and every client this login can see. One portal login is a "client access" and may cover more than one client — a parent seeing two children, say — so clients is always a list.

Appointments from the Client Portal. status "scheduled" returns confirmed/upcoming ones; "requested" returns those still awaiting the practice's confirmation. Pages by number.

Invoices, statements, superbills, receipts, or account history from the Client Portal. An empty list is a real answer — many practices bill entirely outside the portal. Pages by cursor: pass the returned nextCursor as "before".

Balance due and per-category counts for the Client Portal account. Cheaper than paging the billing collections just to find out whether anything is there.

Payment methods saved to the Client Portal — brand, last four digits, and expiry. No full card numbers.

Paperwork the practice has sent — consents, questionnaires, contact and insurance forms, Good Faith Estimates, shared files. Use outstandingOnly to see just what still needs the client's attention.

One document request in full, including its body or its questions and the answers already given.

Files the practice has shared through the Client Portal.

Announcements the practice has posted to the Client Portal. readAt is null on unread ones.

Resolves the credential the way real tools do, then makes one authenticated request to clientsecure.me. Reports which source supplied the credential, whether clientsecure.me accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a clientsecure.me-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.