E-commerce integration
WooCommerce Bookings MCP
WP MCP Pro works WooCommerce Bookings in-process rather than through its wc-bookings/v1 routes, so every response is a curated view and every write goes through the calls the plugin's own screens make. Reads come straight from Bookings' storage and availability from the plugin's own slot calculation. create validates and prices a booking exactly as the booking form does, checking the block is bookable, then saves it as the manual booking screen does, without an order; it can email, so it needs confirm:true. update-status moves a booking through WC_Booking::update_status(), so Bookings' emails, order sync and reminders run, and it needs confirm:true. cancel does the same to cancelled and is destructive and off until a site opts in. set-availability-rules replaces a bookable product's own availability rules. Every write is snapshotted, so rollback-operation undoes it and a create's rollback deletes the booking.
In practice
How WooCommerce Bookings work goes with an agent.
WooCommerce Bookings ties each booking to a bookable product, a start and end in store time, an optional resource and person types, and a status that moves through unpaid, pending-confirmation, confirmed, paid, complete or cancelled. The question an agent gets most is whether a slot is free, and that answer has to come from Bookings' own slot calculation, not from reading the calendar. WP MCP exposes that calculation next to the bookable product's settings, such as duration, block cost, capacity, persons and resources, so a booking is made against the same rules the booking form uses.
Which bookable products do we have, and how are they priced and limited?
Runs bookings.products through woo-read: duration and unit, base and block cost, capacity, whether confirmation is required, persons, resource ids and default availability. A read, so nothing is snapshotted.
Show free slots for product 88 over the next two weeks.
Runs bookings.availability with from and to, which returns the product's own availability rules and the available and booked count per slot. One call covers at most 31 days, and resource_id narrows it.
Book product 88 for Saturday at 14:00, two people, as unpaid.
Runs bookings.create with confirm:true. It is checked and priced the way the booking form does it, and saved without an order. The booking is snapshotted as a creation, so rollback-operation deletes it.
Close product 88 on 24 and 25 December.
Runs bookings.set-availability-rules, which replaces the product's own rules, so the agent reads the current rules from bookings.availability first. The old rules are snapshotted and restored by rollback-operation.
What your AI can do
Real WooCommerce Bookings operations, every write reversible.
- Read bookings and compute availability from the plugin's own slot calculation
- Create a booking, validated and priced as the booking form does, without an order
- Move a booking through its statuses so Bookings' emails and order sync run
- Cancel a booking (off until a site opts in)
- Replace a bookable product's availability rules
- Roll back any write, deleting a created booking on undo
Example prompts
Example WooCommerce Bookings prompts.
Is there availability for the kayak rental next Saturday afternoon?
Create a confirmed booking for product 88 next Saturday at 2pm for two people.
Mark booking 5130 as complete.
Under the hood
The WooCommerce Bookings calls, under the hood.
woo-read({ op: "bookings.availability", params: { product_id: 88, from: "2026-11-14", to: "2026-11-21" } }), the plugin's own slot calculation
woo-write({ op: "bookings.update-status", params: { id: 5130, status: "complete" }, confirm: true }), snapshotted; emails and order sync run
Safety and access
What can be undone on WooCommerce Bookings, and what costs what.
Recoverable on WooCommerce Bookings
- Every booking write is snapshotted, so rollback-operation undoes it.
- Undoing bookings.create deletes the booking it made.
- Undoing set-availability-rules restores the product's previous rules.
- Undoing a status change or a cancel restores the booking and its order's status.
WooCommerce Bookings limits and opt-ins
- bookings.cancel is destructive: it is off until a site enables it with the wpmcp_woo_op_enabled filter, needs confirm:true, and answers recoverable:false.
- A cancel emails the customer, a calendar sync removes the event, and an order holding only that booking is cancelled. Rollback restores the booking and the order status, but not the email or the synced event.
- bookings.create and bookings.update-status both need confirm:true because Bookings can email.
- A new booking can start as confirmed, unpaid, pending-confirmation or paid. A single set-availability-rules call takes up to 100 rules.
Free or Pro: The bookings.* ops are Pro, in the extended WooCommerce toolset behind woo-read, woo-write and woo-ops. The free plugin keeps the core WooCommerce tools. Writes are on by default on a licensed site; create and update-status ask for confirm:true, and cancel is the opt-in. If WooCommerce Bookings is not active, each op answers plugin_missing or plugin_inactive with a link to the plugins screen.
Part of WP MCP Pro
The WooCommerce Bookings integration is part of WP MCP Pro.
One Pro licence unlocks the WooCommerce Bookings tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
WooCommerce Bookings MCP: questions, answered.
Does creating a booking charge anyone?
No. create saves the booking the way the manual booking screen does, with no order and no payment. It can send Bookings' own emails, so it needs confirm:true.
On WooCommerce Bookings, is a cancellation reversible?
Rollback restores the booking and its order's status, but the cancellation emails have gone out and a calendar sync has removed the event, so cancel reports recoverable:false and is off until a site opts in.
What status can a new booking start in?
confirmed by default, or unpaid, pending-confirmation or paid. complete and cancelled are not offered at creation. Afterwards bookings.update-status moves a booking among unpaid, pending-confirmation, confirmed, paid and complete, and ending one is bookings.cancel's job, from unpaid, pending-confirmation, confirmed or paid.
How far ahead can availability be checked?
One bookings.availability call covers at most 31 days. It starts at today unless from is given and ends seven days later unless to is given. To look further ahead, call it again with the next window; hide_unavailable, resource_id, page and per_page narrow each response.
What happens to the order when a booking is cancelled?
Bookings cancels an order that holds only that booking and emails the customer, and a calendar sync removes the event. Rolling back restores the booking and the order status, but the email and the removed event stay gone. That is why cancel reports recoverable:false.
What does reading one booking return?
bookings.get returns the status, product, resource, customer, order, start and end in store time, all-day flag, persons, cost, note and attendance, as a curated view read from Bookings' storage. bookings.list filters by status, product, customer, resource and a from and to date, with pages of up to 50.
Related integrations
More integrations for the same agent.
MCP for WooCommerce
FreeE-commerce, 9 tools.
MCP for WooCommerce Subscriptions
ProE-commerce, 3 tools.
MCP for WooCommerce Memberships
ProE-commerce, 3 tools.
MCP for FiboSearch
FreeE-commerce, 2 tools.
MCP for WP Simple Pay
FreeE-commerce, 1 tools.
MCP for Stripe
ProE-commerce, 2 tools.
Browse the full Integrations hub, or read more on MCP for WooCommerce and the WordPress MCP plugin.