Log inSubmit server
Simplepractice MCP logo

Simplepractice MCP

Read-only MCP access to SimplePractice client-portal appointments, billing, documents, announcements, and sign-in.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Simplepractice MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "simplepractice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "simplepractice-mcp"
      ],
      "env": {
        "SIMPLEPRACTICE_PRACTICE": "YOUR_VALUE_HERE",
        "SIMPLEPRACTICE_SESSION_FILE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_ELICITATION": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 15 tools correctly (Today).

Overview

The simplepractice-mcp MCP server connects AI clients to the SimplePractice Client Portal through its JSON:API. It provides read-only tools for appointments, billing records, payment methods, document requests, shared documents, announcements, account details, and session management. Sign-in uses a one-time emailed link or six-digit PIN, with the resulting session stored locally. Reach for it when an agent needs to inspect a client portal without browser automation or mutation capabilities.

Use cases

  • Review upcoming or requested client appointments
  • Check balances, invoices, receipts, and payment methods
  • Track outstanding paperwork and read document-request answers
  • Inspect shared documents and unread practice announcements
  • Verify portal credentials and session reachability

Key features

  • Read-only SimplePractice client-portal access
  • Appointment and billing retrieval
  • Document request and shared-file listing
  • Announcement and account inspection
  • Magic-link and PIN sign-in
  • Local session persistence and health checks

Tools15

What Simplepractice MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 55d

What it can do

From the 15 tools this server returned when we ran it; 15 declare their own safety hints.

Can delete or modify data · 4Handles credentials · 4Makes network requests · 13Read-only tools · 11
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age68 days
Maintainers1

Observed 2026-11-01 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17d ago via OSV.dev · simplepractice-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed15Callable tools this server registers over MCP.

How Simplepractice MCP works

What the simplepractice-mcp MCP server does

The simplepractice-mcp MCP server exposes the client-facing SimplePractice portal, not the clinician application. Its tools retrieve account information, appointments, billing records, payment methods, paperwork requests, shared files, and practice announcements. The available data belongs to the signed-in client account and can include every client covered by that login.

All portal data operations are read-only. The server does not cancel appointments, sign documents, make payments, or otherwise change portal records. Those actions remain in the SimplePractice portal itself.

How it works

The simplepractice-mcp MCP server communicates with the portal’s JSON:API over HTTP. Authentication does not use a password. Instead, the user receives a one-time sign-in link by email or uses a six-digit PIN. Verifying the link exchanges it for a session cookie, which the server saves for later runs.

A complete sign-in link identifies both the practice and token. The server accepts links on the expected *.clientsecure.me hosts, including the mobile-app form, and rejects unrelated hosts. Links expire after 24 hours and cannot be reused. Sessions have no refresh token, so the user must authenticate again when the session expires.

Most record-oriented tools accept a view value. compact is the default and returns a reduced projection where one exists; full returns the upstream record without that reduction. Document listing does not use this option and returns file references, including shared scans as .jpg files.

Setup and configuration

Install the package globally with npm install -g simplepractice-mcp. No practice must be configured for the initial sign-in because the practice is taken from the link. SIMPLEPRACTICE_PRACTICE can optionally pin operation to a practice slug or host, while SIMPLEPRACTICE_SESSION_FILE changes the session-file location. The default is ~/.simplepractice-mcp/session.json, written with mode 0600.

Requesting a new sign-in email requires confirmation because it sends a real message. Confirmation behavior can be controlled with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET. On clients without confirmation prompts, the first request returns a preview and one-time token; a repeated request with unchanged arguments sends the email.

Tools and capabilities

The simplepractice-mcp MCP server includes tools for:

  • Reading account, practice, client coverage, cancellation policy, and feature permissions.
  • Listing scheduled or requested appointments with clinician and location details.
  • Listing invoices, statements, superbills, receipts, and account history.
  • Checking the balance due and billing-category counts.
  • Listing saved payment-card metadata such as brand, last four digits, and expiry.
  • Listing document requests, optionally restricted to outstanding requests, and retrieving one request with its questions and answers.
  • Listing documents shared by the practice and reading announcements with unread counts.
  • Checking session status, requesting or verifying sign-in credentials, signing out locally, and testing credentials and upstream reachability.

Limitations and notes

The simplepractice-mcp MCP server only forgets the locally stored session when simplepractice_sign_out runs; it does not sign out other browsers, apps, or copies of the server. A copied session can remain usable until SimplePractice expires it. The health check reports failures as returned data rather than raising exceptions.

The project documents that the portal may return HTML for undefined API paths, and that billing pagination uses cursors while appointment pagination uses page numbers. The package has no browser dependency and can run anywhere its HTTP requests and email-based sign-in are available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Simplepractice MCP

simplepractice-mcp is an MCP server that connects AI clients to the SimplePractice Client Portal through its JSON:API. Its main tools read account details, appointments, billing items, payment methods, document requests, shared documents, announcements, and session status. It is read-only; payments, cancellations, and signing remain in the portal.

Install it with `npm install -g simplepractice-mcp`. No required environment variables or browser dependency are documented. After installation, sign in through the Client Portal flow using an emailed one-time link or six-digit PIN.

Sign in by verifying a SimplePractice one-time link or six-digit PIN. Pass the complete emailed link to `simplepractice_verify_sign_in_token`, or request a new link with `simplepractice_request_sign_in_link` and the practice name. The resulting session is saved locally.

Yes, simplepractice-mcp is read-only for portal records. It can retrieve appointments, billing information, documents, announcements, and account data, but it cannot cancel appointments, sign paperwork, or make payments.

Because Claude Desktop cannot show the server’s confirmation prompt, requesting a sign-in email uses a preview and confirmation-token flow controlled by `MCP_CONFIRM_MODE`.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSimplepractice MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/simplepractice-mcp?style=directory)](https://allmcps.com/mcp/simplepractice-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/simplepractice-mcp"><img src="https://allmcps.com/api/badge/simplepractice-mcp?style=directory" alt="Simplepractice MCP on AllMCPs" /></a>