Without WebMCP
Operate the ordinary page controls. The run document registers no WebMCP tools.
Start without WebMCPConsumer app / complete journey
See how an agent can help someone find a time, prepare a booking and check a reservation—with the person in control of confirmation.
Same website. Same task.
Use the same agent and model in a fresh conversation for each run. Both modes use the same calendar and confirmation flow.
Find the earliest available portfolio-review appointment on October 14, 2026, before noon UTC. Prepare it for my review and stop before confirming. Wait for me to confirm using the page. After I confirm, look up the reservation and report its reference, date, time and status.
Operate the ordinary page controls. The run document registers no WebMCP tools.
Start without WebMCPA supported browser agent can call the page’s structured tools. Ordinary controls stay available.
Start with WebMCPWhat happens under the hood
The calendar controls, JSON runner and registered WebMCP tools call the same booking engine. Select a different service in the page, then run get_booking_state: the tool reads exactly that selection.
Confirm a 09:00 appointment and that time becomes unavailable for the selected service. Look up the reference to see its status. Confirm a cancellation and the slot opens again. Trying to book an unavailable time returns an error without changing the reservation.
Write tools require the current revision. Change the calendar, then run an old request to see it rejected. A real booking service must also enforce availability, identity and concurrent reservations on the server.
Try it with a browser agent
Find an introduction call on October 12, 2026 at 09:00 UTC. Prepare it for my review. After I confirm, check the reservation status.
Open this page in a supported WebMCP environment and use its agent or tool inspector. The page reports whether native tools registered. Starting the guided example alone does not test an AI agent.
Set up browser supportNo. This is a working browser-local application with fictional services and a fixed demo calendar. There is no provider API, payment, email, account or external reservation. Reloading clears the history.
The healthcare playground teaches how to prepare a slot without patient information. This consumer booking example adds the full lifecycle: changing availability, reservation references, lookup, cancellation and stale-request handling.
WebMCP exposes app actions to agents; it is not a search ranking shortcut. This page also supplies readable HTML, clear explanations and a crawlable URL. Read the WebMCP SEO guide for the distinction.
API references reviewed September 8, 2026.Chrome imperative API
Tools exposed by this demo
Show fictional studio availability for a service and date in UTC. Updates the visible calendar and clears any unconfirmed review.
Prepare an available slot for visible user review. Does not book. Read get_booking_state for the current revision before calling.
Read a fictional reservation created in this page session, including its confirmed or cancelled status. Does not contact a provider.
Prepare cancellation of a confirmed local reservation for visible user review. Does not cancel it until the user confirms on the page.
Read the visible calendar, available slots, pending review, reservation history and revision. All data is fictional and local to this page.
Reset the fictional calendar, reviews and reservation history in this page only.