Simplepractice MCP server

Read from the package source without running it. The installed server may list more.

• simplepractice_get_account

  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.

• simplepractice_get_billing_overview

  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.

• simplepractice_get_document_request

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

• simplepractice_list_announcements

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

• simplepractice_list_appointments

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

• simplepractice_list_billing_items

  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".

• simplepractice_list_document_requests

  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.

• simplepractice_list_documents

  Files the practice has shared through the Client Portal.

• simplepractice_list_payment_methods

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

• simplepractice_request_sign_in_link

  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 requires confirm:true. A success does not prove the address has an account: the API answers identically for unknown addresses by design.

• simplepractice_session_status

  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.

• simplepractice_sign_out

  Discard the stored Client Portal session from local state.

• simplepractice_verify_sign_in_pin

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

• simplepractice_verify_sign_in_token

  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.

• Code scan19 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Simplepractice: common questions

Is Simplepractice MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Simplepractice safety report

How do I install Simplepractice?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Simplepractice need an API key?

No secret keys are declared. It reads 2 settings from the environment.

Is Simplepractice maintained?

The last commit was in the last day (2026-09-19). The latest release is v1.0.0.