Yoya exposes scheduling tools through the Model Context Protocol (MCP). Your AI client can read a host’s booking page and availability, then submit a booking once you have chosen a time. The host needs a Yoya booking page. You do not need a Yoya account to book as their guest.
1. Connect the public booking server
In your terminal, add the remote HTTP server:
claude mcp add --transport http yoya-book https://yoya.ai/api/mcp/bookOpen Claude Code in the same project and use /mcp to check its connection status. This command adds the public booking server, which does not require Yoya sign-in.
2. Check the page before choosing a time
Replace the example below with the actual link your host shared. Ask your assistant:
Look up this Yoya booking link. Tell me the host, meeting length, available meeting options, and required fields. List available times in Asia/Shanghai. Do not book yet.
The assistant should first call get_booking_page, then list_available_times. The first response includes the host’s time zone and any required fields. The second includes available slot IDs and time labels.
Time-zone detail: MCP time labels are in the host’s time zone. Ask the assistant to convert them to your IANA time zone, such as Asia/Shanghai or America/Los_Angeles, and show the date as well as the time. Conversion can change the day.
3. Confirm your details and book
Choose one of the returned times. Provide your name, email address, meeting purpose, and any fields the host requires. If several meeting options are offered, choose one.
Before approving the booking tool call, check the host, calendar date, start time, time zone, meeting length, and email address. The assistant must pass the selected slotId from the availability response to book_meeting; a time written in plain text is not a substitute.
A successful reservation may still have pending calendar or notification delivery. Keep the returned management link and open it for the latest meeting details. Do not request a second booking just because an email has not arrived.
4. Recover from a changed slot
If the server returns slot_taken or slot_unknown, ask for fresh availability and choose again. If it reports quota_exceeded, the host cannot accept more bookings under their current allowance. Changing clients will not remove that limit.
Clients implementing retries can send a UUID requestId and reuse it for the same confirmed request. The management link includes a private token; keep it out of public screenshots and shared prompts.
Managing your own booking pages
The separate management server is https://yoya.ai/api/mcp. It requires Yoya sign-in through OAuth and can manage your pages, hours, date overrides, and bookings. Connecting the public booking server does not grant access to your dashboard.
See the MCP overview for management setup. Google Calendar and Zoom connections are configured in Yoya; adding an MCP server does not connect those accounts for you.
What we checked
On September 5, 2026, we connected to the production public endpoint with MCP SDK 1.29.0 over Streamable HTTP. Tool discovery returned get_booking_page, list_available_times, book_meeting, and get_booking. A read-only lookup of our Leo page and its availability succeeded. An unauthenticated request to the management endpoint returned HTTP 401.
This check did not create a booking, complete OAuth, or test the desktop client interface end to end. Setup instructions were checked against the client’s documentation. Client versions and account policies can affect connection behavior.
Claude Code MCP documentation · Product demo · Yoya plans
For a first experiment, use your own Yoya page and stop after listing availability. A real booking reserves the host’s time and may send invitations.