YouCanBookMe MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YCBM_API_KEY | Yes | Your API key (HTTP basic auth password) | |
| YCBM_BASE_URL | No | Override for testing | https://api.youcanbook.me |
| YCBM_ACCOUNT_ID | Yes | Your account ID (HTTP basic auth username) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_booking_pagesA | List the account's booking pages (the API calls them profiles). Returns each page's id, title and subdomain. The subdomain is what find_available_times needs. |
| get_booking_pageB | Get one booking page's settings. Use |
| search_bookingsA | Search bookings in a time range, optionally by status, booking page, or text (booker name/email in the form, title, or booking ref). Returns counts by status and page plus a compact list with booker name and email. Set raw=true for YCBM's full objects. |
| list_upcoming_bookingsA | List upcoming (not cancelled) bookings for the next N days, soonest first, with booker name and email. |
| get_bookingA | Get one booking with times, status, booking page, and the booker's form answers. |
| find_available_timesA | Find open times on a booking page, grouped by day with readable local times. This starts a booking intent and returns its intentId. Pass that intentId and one slot's exact startsAt to book_time to book it. |
| book_timeA | Book a slot found by find_available_times. Fills the booking form and confirms the intent, which creates a real booking and calendar event and sends notifications, so confirm details with the user first. |
| reschedule_bookingA | Move a booking to a new start time. Use find_available_times first to pick a free slot. The booker is notified, so confirm with the user first. |
| cancel_bookingA | Cancel a booking as the calendar owner. The calendar event is removed and cancellation notifications are sent per the page's settings. Confirm with the user first. |
| delete_bookingA | Permanently delete a booking record from YouCanBookMe. No further notifications are sent, but the calendar event stays on the calendar. Prefer cancel_booking unless the user explicitly wants the record gone. |
| booking_reportA | Counts of bookings in a period by status (finished, cancelled, noShow, upcoming...) and by booking page. Good for 'how many no-shows did we have last month?'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target clearly distinct operations (get_booking vs get_booking_page, cancel_booking vs delete_booking, find_available_times vs book_time). The main overlap is between search_bookings, list_upcoming_bookings, and booking_report, all of which return booking information, but their descriptions clarify different use cases well enough.
The set is mostly consistent snake_case with a verb_noun pattern (get_booking, cancel_booking, list_booking_pages, find_available_times). Minor deviations like booking_report (noun_noun) and book_time (verb_noun but less explicit) are readable but slightly break the pattern.
Eleven tools is well-scoped for a booking management server. Each tool covers a distinct part of the booking workflow—discovery, availability, booking, modification, cancellation, deletion, and reporting—without obvious redundancy.
The server covers the full booking lifecycle for existing pages: list/get pages, search/get bookings, check availability, book, reschedule, cancel, delete, and report. It lacks booking page creation/update settings and possibly booking note/comment operations, but core agent workflows are well supported.