Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Vagaro to Claude Code

Make Claude surface appointments and client details in Vagaro. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Vagaro to Claude Code?

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

claude mcp add --transport http vagaro 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 Vagaro once connected?

A scoped Vagaro connector lets Claude retrieve appointment details, look up client profiles and contact info, check staff availability, manage employee calendar assignments, and react to webhook events. The lookups that used to mean switching screens happen where your business already runs, with bookings still made in Vagaro.

  • Look up appointment details such as status, start time, and who is providing the service
  • Pull up a client profile, contact details, and any tags on their account
  • Check a staff member's availability and surface open slots to book in Vagaro
  • Assign or unassign an employee to provision or deprovision their calendar
  • Draft a confirmation or follow-up message for you to send from Vagaro
  • React to a webhook event and summarize what changed on the calendar

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 Vagaro 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 Vagaro API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Vagaro 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 Vagaro 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 Vagaro 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 Vagaro 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 Vagaro'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 Vagaro?
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 Vagaro account it signs in with. Revoking access is one click in Vagaro.

More on the Vagaro connector

Vagaro connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + 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