simplepractice-mcp

MCP server for the SimplePractice Client Portal — the side a practice's clients log into, not the clinician side. Appointments, billing, paperwork, and announcements, read over the portal's own JSON:API.

Developed and maintained by AI (Claude Code). Use at your own discretion.

What it reads

Tool	What it gives you
`simplepractice_get_account`	practice, current client, every client this login covers, cancellation policy, feature permissions
`simplepractice_list_appointments`	scheduled or requested appointments, with clinician and location
`simplepractice_list_billing_items`	invoices · statements · superbills · receipts · account history
`simplepractice_get_billing_overview`	balance due and per-category counts
`simplepractice_list_payment_methods`	saved cards — brand, last four, expiry
`simplepractice_list_document_requests`	paperwork sent to you, with an outstanding-only filter
`simplepractice_get_document_request`	one request in full, with its questions and answers
`simplepractice_list_documents`	files the practice has shared
`simplepractice_list_announcements`	practice announcements, with unread counts
`simplepractice_session_status` · `_request_sign_in_link` · `_verify_sign_in_token` · `_verify_sign_in_pin` · `_sign_out`	sign-in
`simplepractice_healthcheck`	Verify credentials and upstream reachability; reports failures as data, not exceptions

Everything is read-only. Cancelling, signing, and paying happen in the portal.

The reads that answer with a SimplePractice record rather than a projection — appointments, billing items, the billing overview, one document request, announcements — take a view. It defaults to compact, which returns the slim projection where this server has one and otherwise drops logo and avatar URLs a model cannot see; view: "full" returns the record untouched. simplepractice_list_documents deliberately takes none: what it returns is the file reference, and a shared scan is a .jpg.

Setup

npm install -g simplepractice-mcp

There is nothing to configure. The practice comes from your sign-in link.

Variable
`SIMPLEPRACTICE_PRACTICE`	optional — pins the server to one practice (slug or host)
`SIMPLEPRACTICE_SESSION_FILE`	optional — session path (default `~/.simplepractice-mcp/session.json`, written `0600`)

Signing in

The Client Portal has no password. SimplePractice emails a one-time link (or a 6-digit PIN); you trade it for a session cookie:

Open the email your provider sent, copy the link.
simplepractice_verify_sign_in_token { link } — pass the whole link.

The link is https://<practice>.clientsecure.me/sign-in/token#<TOKEN>, so one paste carries both halves of what the server needs: the token is the # fragment, and the host names the practice. Nothing is hardcoded, and the stored session remembers the practice for every later run — simplepractice_session_status reports which practice is in play and whether it came from a link, the environment variable, or the saved session.

To have a fresh link sent rather than using one you already have, name the practice once:

simplepractice_request_sign_in_link { email, practice: "achievebalancetherapy", confirm: true }

practice can be omitted whenever the server already knows the practice — from an earlier sign-in, or from SIMPLEPRACTICE_PRACTICE.

Two sign-in links name no practice, and fall back to whichever one is already known: the mobile-app variant SimplePractice sends (https://clientsecure.me/client-portal-api/sign-in/token#<TOKEN>, pointed at the bare apex), and a bare token pasted without its link. A link on any host outside *.clientsecure.me is never adopted — the token is not sent there.

Links are single-use — replaying one answers 401 "Authorization has already been used or expired" — and last 24 hours. The request endpoint is rate-limited per address and per IP, which is why sending is confirm-gated: a retry loop locks you out of the only way in. There is no refresh token; when the session lapses, you sign in again.

The whole chain is verified end to end against a live portal — request, the emailed link, the exchange returning verified plus a session cookie, and an authenticated read with that new session.

Because that flow needs nothing but HTTP and your inbox, this server has no browser dependency and can run anywhere.

Without the server

skills/simplepractice-fpx does the same reads with curl, either signing in by magic link or lifting the session cookie from a browser tab with fpx.

Notes from building this

The portal is an Ember app that ships public sourcemaps, so its models, adapters and routes are readable directly — docs/SIMPLEPRACTICE-API.md records the endpoints and the traps, all confirmed against a live portal:

The SPA catch-all answers HTTP 200 with text/html for any path the API does not define. /cards and /client-billing-overviews look like working, empty endpoints and are not endpoints at all — both are include relationships of /clients/<id>.
hasDocumentPdf, a card's isDefault, and the client's permissions blob are all strings, not booleans or objects.
Billing pages by cursor (page[before] = a row's cursorId), appointments page by number. The two are not interchangeable.

Development

npm install
npm run build
npm test              # 214 tests
npm run test:coverage # 100% enforced
npm run typecheck     # vitest does not run tsc — this does

License

MIT

simplepractice mcp