← Back to all docs
simplepractice

SimplePractice MCP Server

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.

By Alex KlarfeldMay 12, 2026
SimplePractice MCP Server

What is the SimplePractice 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.

What you can do with SimplePractice via MCP

Once connected, an agent can:

  • Look up clients: demographics, contacts, portal status, insurance.
  • Pull and create appointments and sessions: office, telehealth, group.
  • Retrieve clinical notes and treatment plans, with signatures and lock state.
  • Get intake forms and documents: consents, questionnaires, attachments.
  • Pull services and fee schedules: CPT, POS, modifiers.
  • Submit insurance claims (837P) and reconcile remittances (835).
  • Retrieve payments, invoices, and superbills.

How to connect SimplePractice to Claude, ChatGPT & Cursor

Connecting works like any other MCP server. The short version:

  • Claude (Desktop or claude.ai): add the SimplePractice MCP server under Settings → Connectors (or your MCP config), authorize the SimplePractice account Supergood provisions, and the tools show up in any chat, including agent runs.
  • ChatGPT: add it as a connector under Settings → Connectors, authorize, and ChatGPT can call the SimplePractice tools in conversations and in agent mode.
  • Cursor: add the server to your MCP config (mcp.json or Settings → MCP), reload, and the tools are available to the agent.

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.

How Supergood builds the SimplePractice MCP server

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.

  • Auth and MFA, handled. Supergood provisions a dedicated SimplePractice account (email and phone managed by us) and keeps the session alive through MFA, token expiry, and re-auth.
  • Normalized data. Responses come back in consistent JSON shapes across modules, not the raw shape SimplePractice's front-end happens to return.
  • Monitored and adapted. When SimplePractice changes its web and portal UI or internal API, monitoring catches it and the connector gets patched, usually before it reaches you.
  • No public API, no problem. SimplePractice never shipped a developer API; Supergood works the authenticated web and portal flows directly, handling 2FA and session refresh.

Getting Started

  • Schedule Integration Assessment

Book a 30-minute call to confirm which SimplePractice modules and workflows you need and how authentication should work.

  • Supergood Builds and Validates Your MCP Server

We deliver a hardened SimplePractice connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as SimplePractice changes.

Use Cases

Practice-ops agent

- 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

Documentation

- 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

Billing and RCM

- Submit claims and reconcile ERAs - Surface denials and missing-info rejections - Reconcile payments against superbills

Client portal sync

- Mirror booking and messaging activity into another tool - Keep portal status in sync - Surface new client requests

Technical Specifications

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.

Frequently asked questions

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.

Ready to get a real API?