Connect SimplePractice to Claude Code
Have Claude draft session notes and prepare client work in SimplePractice. From the terminal, inside the sessions where you already work.
How do you connect SimplePractice to Claude Code?
Claude Code reaches outside tools through MCP servers. To connect SimplePractice, you add a SimplePractice MCP server: a small hosted service that exposes SimplePractice's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own SimplePractice account. No API keys pasted into config files.
claude mcp add --transport http simplepractice https://your-connector-url/mcpThen run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.
What can Claude Code do in SimplePractice once connected?
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
One connector, every Claude surface
The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same SimplePractice access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.
Build it yourself, or have it built?
If you live in the terminal, you can absolutely write your own MCP server against the SimplePractice API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SimplePractice changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build SimplePractice connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.
Frequently asked questions
Does the same SimplePractice connector work in claude.ai and Claude Code?
Do I need to host or maintain anything myself?
Is it safe to give a coding agent write access to SimplePractice?
More on the SimplePractice connector
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.