Simplepractice MCP server
SimplePractice Client Portal — appointments, billing, documents, announcements
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Simplepractice yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Simplepractice tools
No tool declarations could be read from the package source. They show once the server is installed.
How Simplepractice compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
Release history: 14 versions in the registry since 2026-09-10, latest 2026-10-16, typically one every 2 days.
Install Simplepractice in Claude Code, Cursor or VS Code
Runs npx -y simplepractice-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add simplepractice-mcp -- npx -y simplepractice-mcp
What the publisher says
From the Simplepractice repository's README, as published. We do not edit it. Read it on GitHub
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
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. simplepracticelistdocuments deliberately takes none: what it returns is the file reference, and a shared scan is a .jpg.
Setup
npm install -g simplepractice-mcpThere is nothing to configure. The practice comes from your sign-in link.
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.
- simplepracticeverifysignintoken { link } — pass the whole link.
The link is https://.clientsecure.me/sign-in/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 — simplepracticesessionstatus 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#, 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Simplepractice: common questions
- Is Simplepractice MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Simplepractice safety report
- How do I install Simplepractice?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop 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 32 days ago (2026-10-03). The latest release is v1.2.7.