The SimplePractice MCP server lets AI agents read and write client, scheduling, documentation, and billing data in SimplePractice. Connect SimplePractice to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since SimplePractice doesn't ship an MCP server.

The SimplePractice MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write client, scheduling, documentation, and billing data in SimplePractice through a standard protocol.
In short: SimplePractice is a cloud EHR and practice-management platform for solo and group practices in behavioral health and related outpatient care: scheduling, a client portal, paperless intake and e-signatures, HIPAA-compliant telehealth, clinical documentation, and insurance billing.
SimplePractice doesn't ship an official MCP server, and SimplePractice has historically had no formal public API or webhooks (practitioners have long asked for one), so a reverse-engineered connector is the realistic path to programmatic access. Supergood builds and maintains the connector by reverse-engineering SimplePractice's authenticated web and portal flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.
Once connected, an agent can:
Connecting works like any other MCP server. The short version:
Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.
Supergood doesn't wait for SimplePractice to ship an API. We reverse-engineer the authenticated web and portal flows behind SimplePractice, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.
Book a 30-minute call to confirm which SimplePractice modules and workflows you need and how authentication should work.
We deliver a hardened SimplePractice connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.
Go live with continuous monitoring and automatic adjustments as SimplePractice changes.
- Answer "who's on my schedule and which intakes are outstanding" - Send and chase intake forms and consents - Confirm contact and insurance details before the session
- Pull the open session note and the treatment plan - Surface notes that still need a signature or are still unlocked - Keep records consistent with another system
- Submit claims and reconcile ERAs - Surface denials and missing-info rejections - Reconcile payments against superbills
- Mirror booking and messaging activity into another tool - Keep portal status in sync - Surface new client requests
MCP transport
Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.
Authentication
Supergood provisions a dedicated SimplePractice account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.
Supported clients
Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.
Tools exposed
8 tools covering the workflows listed above; the set is scoped to the modules you license.
Data freshness
Near real-time reads and writes against SimplePractice's live web app and client portal.
Rate limits
Tuned to SimplePractice's tolerances; Supergood paces requests to avoid tripping security throttles.
Latency
Sub-second for most reads under normal load; writes reflect the underlying platform timing.
Session management
Automatic re-auth plus cookie/token rotation, with health checks.
Security
Encrypted transport, scoped access, and audit logging; respects SimplePractice role-based permissions.
Webhooks
Optional asynchronous delivery for long-running operations; polling otherwise.
Reliability
Retry logic, backoff, and idempotency keys to avoid duplicates.
Adaptation
Continuous monitoring for SimplePractice web and portal surfaces changes, with rapid connector updates.
No. SimplePractice doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering SimplePractice's authenticated flows and exposing them as MCP tools, plus the underlying REST API.
All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.
Supergood provisions a dedicated SimplePractice account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.
Yes. Reads and writes hit SimplePractice's live system, not a nightly export. SimplePractice has historically had no formal public API or webhooks (practitioners have long asked for one), so a reverse-engineered connector is the realistic path to programmatic access.
Both. The MCP tools are a layer on top of a normalized REST API for SimplePractice; you can call either, from an agent or from your own code.