Skip to content
Custom Connectors

Connect Microsoft Bookings to Claude Code

Let Claude book, reschedule, and cancel appointments in Microsoft Bookings. From the terminal, inside the sessions where you already work.

How do you connect Microsoft Bookings to Claude Code?

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

claude mcp add --transport http microsoft-bookings 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 Microsoft Bookings once connected?

Full read-write Microsoft Bookings access lets Claude create an appointment in a booking calendar, assign the right staff member, reschedule or cancel an existing booking, and adjust services and availability, once you approve. The coordination that used to mean clicking through the Bookings page happens where you are already working.

  • Create an appointment in a specific booking calendar with the service and staff you choose
  • Reschedule an existing booking to a new time after you confirm
  • Cancel a booking and trigger the standard customer notification once you approve
  • Assign or reassign a staff member to a scheduled appointment
  • Look up upcoming appointments across a booking calendar and surface gaps or conflicts
  • Update a service definition, such as its duration or default staff, on your instruction

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

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.