Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Phorest to Claude Code

Make Claude book appointments and manage clients in Phorest. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Phorest to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Phorest, you add a Phorest MCP server: a small hosted service that exposes Phorest'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 Phorest account. No API keys pasted into config files.

claude mcp add --transport http phorest https://your-connector-url/mcp

Then 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 Phorest once connected?

Full read-write means Claude can pull a client's visit history, check appointment availability, and create the booking in one conversation. It can add new clients from enquiries, update contact details, and report on a staff member's week, with every change to the diary held for your approval.

  • Look up a client and summarize their visit history, purchases, and courses
  • Check availability and create an appointment booking, after you approve
  • Add a new client to your Phorest client list from an enquiry, after you approve
  • Update a client's contact details or notes, after you approve
  • List a staff member's appointments for the week and flag open slots
  • Pull the product list with stock levels, cost, and sale price for a salon

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 Phorest 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 Phorest API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Phorest 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 Phorest 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 Phorest connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Phorest account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Phorest's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Phorest?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Phorest account it signs in with. Revoking access is one click in Phorest.

More on the Phorest connector

Phorest connector for claude.aiVagaro + Claude CodeMindbody + Claude CodeSetmore + Claude Code

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.

Build my connectorTalk to us