Full read-write Claude connector for SimplePractice
Have Claude draft session notes and prepare client work in SimplePractice
Stop tabbing through SimplePractice to document and prepare client items by hand. Where a sanctioned access path is available, Claude drafts notes and prepares messages, reminders, and invoice line items right where the work lives, with every save and client-facing send gated behind your approval.
SimplePractice is a practice management platform for health and wellness professionals like therapists, counselors, and dietitians, covering clients, scheduling, documentation, billing, and telehealth. Practices want Claude to do more than read a chart: to draft notes, prepare client-facing items, and move admin forward inside the client record.
What is a SimplePractice MCP server?
A SimplePractice MCP server is a small hosted service that exposes SimplePractice's data and actions to Claude over the Model Context Protocol, so Claude can industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can SimplePractice's current connector do today?
Today, SimplePractice does not ship a first-party Claude or MCP connector, and it offers no public developer API for individual practices: no documented REST API and no webhooks. The only first-party API is an invite-only Enterprise and Health Plans program, scoped to scheduling and availability for health plans and EAPs. So for a standard account, a Claude connection depends on a sanctioned access path or a Zapier-style workaround, and the actions Claude can take are constrained by what SimplePractice actually exposes.
What does full read-write SimplePractice access unlock?
Where a sanctioned access path is available, a SimplePractice connector can let Claude draft a progress or session note for your review and prepare client-facing items like a message or invoice line item before you send or bill. Much of the value is preparation: Claude assembles the documentation and outbound copy inside your workflow, and you keep the final save and send. What is reachable depends on the access SimplePractice grants your practice.
- Draft a progress or session note tied to a client for your review
- Prepare an intake summary or client contact update for you to apply
- Draft a client message or appointment reminder for you to send
- Prepare an invoice line item before you bill it to a client
- Summarize a client's recent sessions and outstanding follow-ups
- Compile a follow-up task list after a session for you to enter
Can a Claude connector work with SimplePractice at all?
It depends on access. SimplePractice has no first-party Claude integration and no public API for individual practices, only an invite-only Enterprise and Health Plans program scoped to scheduling and availability. So a connection relies on a sanctioned access path or a Zapier-style workaround, and what Claude can do is constrained by what SimplePractice actually exposes to your account.
Can Claude draft progress and session notes in SimplePractice?
Drafting progress and session notes is something Claude can do tied to the right client record for your review. It can also compile a follow-up task list or prepare a client contact and intake update for you to apply. Anything that saves into a record, bills a client, or sends to them stays a separate, gated action that waits for your confirmation.
Will Claude bill or message clients in SimplePractice on its own?
Billing and messaging clients in SimplePractice are gated write actions, not automatic ones. Claude can prepare an invoice line item, a client message, or an appointment reminder, but each is finalized only after you approve it. The connector never has more access than the SimplePractice account it runs as, so nothing reaches a client unreviewed.
How a SimplePractice connector works
SimplePractice has no public per-practice API, so we first confirm a viable access path: a sanctioned Enterprise or partner route, or a Zapier-style workaround your account already supports. We then build a small MCP server that requests only the access the work needs. Read or summarize tools are separated from drafting tools, and anything that bills, sends to a client, or saves into a record is gated behind your confirmation. Claude never has more access than the SimplePractice account it runs as, and we can add IP allowlisting where your practice requires it.
Frequently asked questions
Can Claude draft notes and prepare client work in SimplePractice, not just read clients?
Will Claude send messages to clients or bill them without my approval?
Does the connector get more access to client records than my login has?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.