Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Glofox to Claude Code

Make Claude book members and update memberships in Glofox. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Glofox to Claude Code?

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

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

Full read-write Glofox access lets Claude book or cancel a member's class reservation, create a class or adjust its capacity, update or pause a membership, add or adjust a member's credits, and update a member's profile once you approve. The front-desk admin that used to mean clicking through screens happens where your member data already lives.

  • Book or cancel a member's reservation for a specific class or appointment
  • Add or adjust a member's class credits after you confirm
  • Update, pause, or renew a membership plan after you confirm
  • Update a member's profile with new contact or account details
  • Record a payment against a member's account once you approve
  • Create a new class or adjust the capacity on an existing one

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

More on the Glofox connector

Glofox 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