Skip to content
Custom Connectors

Connect YouCanBook.me to Claude Code

Let Claude reschedule bookings and manage booking pages in YouCanBook.me. From the terminal, inside the sessions where you already work.

How do you connect YouCanBook.me to Claude Code?

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

claude mcp add --transport http youcanbookme 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 YouCanBook.me once connected?

Full read-write YouCanBook.me access lets Claude create or edit a booking page, reschedule or cancel an existing booking, adjust availability and buffer rules, update the questions a booker answers, and route to the right team member, once you approve. The coordination that used to mean opening the YouCanBook.me dashboard happens where you are already working.

  • Create or edit a booking page with the durations, availability, and branding you specify
  • Reschedule an existing booking to a new slot, keeping the booker and form answers intact
  • Cancel a booking and notify the booker after you approve
  • Adjust availability windows, buffers, or notice periods for a booking page
  • Update the intake questions a booker answers before confirming
  • Find every booking matching a query and propose batched changes

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

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.