Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Simplepractice MCP
Overview
Description from the maker (original English)
SimplePractice Client Portal — appointments, billing, documents, announcements
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
SIMPLEPRACTICE_PRACTICE,SIMPLEPRACTICE_SESSION_FILE
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"simplepractice": {
"command": "npx",
"args": [
"-y",
"simplepractice-mcp"
],
"env": {
"SIMPLEPRACTICE_PRACTICE": "your-value",
"SIMPLEPRACTICE_SESSION_FILE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add simplepractice --env SIMPLEPRACTICE_PRACTICE=your-value --env SIMPLEPRACTICE_SESSION_FILE=your-value -- npx -y simplepractice-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"simplepractice": {
"command": "npx",
"args": [
"-y",
"simplepractice-mcp"
],
"env": {
"SIMPLEPRACTICE_PRACTICE": "your-value",
"SIMPLEPRACTICE_SESSION_FILE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"simplepractice": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"simplepractice-mcp"
],
"env": {
"SIMPLEPRACTICE_PRACTICE": "your-value",
"SIMPLEPRACTICE_SESSION_FILE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
SIMPLEPRACTICE_PRACTICEenvOptional. Pins the server to one practice — the slug ("achievebalancetherapy") or the full host. Unset, the practice comes from your emailed sign-in link.SIMPLEPRACTICE_SESSION_FILEenvWhere to persist the signed-in session (default ~/.simplepractice-mcp/session.json, written 0600).
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chrischall, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32568 servers in this category
- Published to the registry more recently than 93% of the other 32568 servers in this category
- Basic checks equal to or better than 100% of the other 32568 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Simplepractice MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.3.1) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
FlyDocs
by flydocs.ai
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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-mcpThere 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:// .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 — 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" }Sending asks you to confirm first (see Confirmations).
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.
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 asks for confirmation first: a retry loop locks you out of the only way in. There is no refresh token; when the session lapses, you sign in again.
simplepractice_sign_out only forgets the session stored on this machine (its entry in session.json). SimplePractice is never told, so the session token stays valid on SimplePractice's side until it expires there — any copy of it (a backup of ~/.simplepractice-mcp, another running copy of this server) keeps working until then. How long that is is SimplePractice's to decide; the 24 hours above is the sign-in link's lifetime, not the session's. It does not sign the Client Portal out anywhere else, such as a browser or the app.
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.
Confirmations
simplepractice_request_sign_in_link sends a real email, so it asks you to confirm first. On a client that can show a confirmation prompt (Claude Code) you get the prompt, unless MCP_CONFIRM_ELICITATION=off. On one that cannot (claude.ai, Claude Desktop), the first call sends nothing and returns a preview — the address, the practice — plus a confirmToken; only a repeat call with that token, and the same arguments, sends. A token works once, and a changed address or practice is refused.
| variable | default | |
|---|---|---|
MCP_CONFIRM_MODE | ask-user | What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse. |
MCP_CONFIRM_ELICITATION | on | off never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE path. Set it for a client that claims to support prompts but never shows one (the write hangs — opencode 2.0.x). Any other value stays on, with a warning on stderr. |
MCP_CONFIRM_TTL_SECONDS | 600 | How long a token stays valid. |
MCP_CONFIRM_SECRET | random per process | Signing key; set it only if tokens must survive a server restart. On mcp-host the host supplies a stable per-child key (MCP_HOST_CONFIRM_SECRET) and spent tokens are recorded under MCP_DATA_DIR, so an approval survives an idle restart. |
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.
/cardsand/client-billing-overviewslook like working, empty endpoints and are not endpoints at all — both areincluderelationships of/clients/. hasDocumentPdf, a card'sisDefault, and the client'spermissionsblob are all strings, not booleans or objects.- Billing pages by *cursor* (
page[before]= a row'scursorId), appointments page by *number*. The two are not interchangeable.
Development
npm installnpm run build npm test # 214 tests npm run test:coverage # 100% enforced npm run typecheck # vitest does not run tsc — this does
License
MIT