Get the plugin
WP MCP/Integrations/Events

Events integration

Amelia MCP

Amelia keeps your booking business in its own tables: categories, services with each employee's price and capacity, employees with their working week, breaks and days off, customers, appointments and events. WP MCP Pro reads all of that straight from those tables, plus free slots from Amelia's own slot calculation, and runs every write through Amelia's own application layer, the controllers its admin pages call, so Amelia's permission, slot and working-hours checks all run and a taken slot or a time outside working hours is refused with Amelia's own reason. It creates and updates categories, services, employees and customers, books, reschedules and sets the status of appointments, creates and updates events, and adds event attendees. Times are site-local in and out, durations are minutes, and anything Amelia Lite cannot store (group capacity, buffer time, more than one person per booking, employees beyond the first) is refused by name rather than silently dropped. Customer emails and SMS are held unless a call asks to notify, and every write is snapshotted as an Amelia rows image first, so a rollback restores Amelia's rows exactly without re-sending anything. Appointments and events are cancelled, never deleted.

plugin-data-readplugin-data-write

In practice

How Amelia work goes with an agent.

Amelia is a booking plugin with its own database tables, so a booking agent cannot just edit posts. What it needs is Amelia's rules: which employee works which hours, how long a service runs, and whether a slot is still free. WP MCP Pro reads Amelia's rows directly, takes free slots from Amelia's own slot calculation, and sends every change through the same application layer the Amelia admin pages use. Times go in and out as site-local "Y-m-d H:i", durations are minutes, and a time that does not exist in a daylight-saving jump is refused instead of guessed.

Which days next week can Dr. Lee do a 45 minute consultation, and are any of them already full?

Runs amelia-list-services to find the service id, then amelia-get-slots with service_id, from and employee_id. The slots come from Amelia's own calculation, so breaks, days off and existing bookings are already accounted for. Read only, nothing is snapshotted.

Book Jane Doe with Dr. Lee on Friday at 14:00 for the consultation, and do not email her yet.

Runs amelia-book-appointment, which goes through Amelia's slot and working-hours checks and is refused with Amelia's own reason if the time is taken. Customer emails and SMS are held unless notify is true, and the response lists the ones that were held. Amelia's rows are snapshotted first.

Dr. Lee is off on the 24th. Add the day off and move his two bookings that morning to the afternoon.

Runs amelia-update-employee with days_off (it replaces the whole list, so the agent reads amelia-list-employees first), then amelia-reschedule-appointment once per booking. Each write is its own snapshotted operation, and every move is rechecked against the new working hours.

Add a Saturday yoga event, 12 places, 9 to 10 in the morning, and sign up Sam for two places.

Runs amelia-create-event with periods and max_capacity, then amelia-add-event-attendee with persons 2. The attendee call is refused when fewer places are left, a check Amelia's own backend booking skips. Both writes are snapshotted.

What your AI can do

Real Amelia operations, every write reversible.

  • Read Amelia services, employees, customers, appointments and events
  • Get free slots by Amelia's own slot calculation
  • Book, reschedule and set the status of an appointment (approved, pending, canceled, rejected)
  • Create and update categories, services, employees and customers
  • Create and update events and add an event attendee, refused when no places are left
  • Hold customer notifications unless a call asks to send them
  • Roll back any Amelia write exactly, with later bookings protected

Example prompts

Example Amelia prompts.

List our services with each employee's price, and show free slots for a haircut over the next week.

Book Jane Doe into the 2pm consultation on Friday with Dr. Lee.

Add a Saturday morning yoga event with 12 places and set it to open.

Under the hood

The Amelia calls, under the hood.

wpmcp, amelia

plugin-data-read({ integration: "amelia", operation: "amelia-get-slots", args: { service_id: 7, from: "2026-11-17", days: 7 } }), Amelia's own slot calculation

plugin-data-write({ integration: "amelia", operation: "amelia-book-appointment", args: {…} }), runs Amelia's slot and working-hours checks; snapshotted, reversible

Safety and access

What can be undone on Amelia, and what costs what.

Recoverable on Amelia

  • Every Amelia write is snapshotted first as an image of the affected Amelia rows.
  • rollback-operation restores those rows exactly and does not re-send any email or SMS.
  • A rollback is refused while later bookings depend on what it would undo, so it cannot orphan a booking made in between.
  • Cancelling an appointment or an event is a status change, so it is restorable like any other write.

Amelia limits and opt-ins

  • Appointments and events are cancelled or rejected, never deleted.
  • Categories, services, employees and customers can be deleted only with confirm:true, and only while nothing uses them. Amelia's own delete would take their appointments or services with it.
  • Amelia Lite cannot store group capacity, buffer time before and after, more than one person per booking, or any employee after the first. Those arguments are refused by name.
  • Customer notifications are held unless a call sets notify:true. Employee and admin notifications still follow Amelia's own settings.

Free or Pro: The whole Amelia integration is Pro. It sits on the plugin-data read and write pair, so it adds no top-level tools: the agent calls amelia-* operations through plugin-data-read and plugin-data-write. On the free plugin those operations are not offered, and list-tool-catalog shows what your site has. Access also follows Amelia's own capabilities (amelia_write_appointments, amelia_read_customers and so on) on top of the plugin's, because customers are personal data.

Part of WP MCP Pro

The Amelia integration is part of WP MCP Pro.

One Pro licence unlocks the Amelia 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

Amelia MCP: questions, answered.

Does it bypass Amelia's booking rules?

No. Every write runs through the same Amelia controllers its admin pages call, so its permission, slot and working-hours checks, its notifications and its calendar and other integrations all run. A taken slot or a time outside working hours is refused with Amelia's own reason.

What about Amelia Lite limits?

Anything Amelia Lite cannot store (group capacity, buffer time before and after, more than one person per booking, and any employee but its first) is refused by name rather than silently dropped, so nothing is lost without you being told.

Will customers get an email when the agent books or moves an appointment?

Not unless you ask. Customer emails and SMS that Amelia would send during a write are held, and the response lists which were sent and which were held. Pass notify:true on the call to let them go. Employee and admin notifications still follow Amelia's own configuration.

How does it handle time zones?

Everything is site-local in and out, written as "Y-m-d H:i", even though Amelia stores appointments in UTC underneath. A local time that does not exist because of a daylight-saving jump is refused rather than shifted. Durations and buffers are whole minutes.

What does amelia-get-setup tell the agent?

It returns the Amelia edition, the site timezone, currency, slot length in minutes, whether a mail sender is configured, and record counts. An agent reads it first so it knows whether Lite limits apply and how slots are sized before it plans any bookings.

With Amelia, can the agent delete a customer who asked to be removed?

Yes, with amelia-delete-customer and confirm:true, but only when nothing uses the customer. A customer with bookings is refused, because Amelia's own delete would remove those bookings with them. Rollback-operation can restore the customer row if it was a mistake.

Point your AI at Amelia.