An agent can list services, employees, customers, events, and appointments, check open time slots for a service, add a new service or customer, create an appointment or event, book a customer into an event, and cancel an existing booking.
Needs WordPress 6.9 or newer with Amelia active. Each ability checks a dedicated Amelia capability or permission-service check for the entity and action involved (read or write access to services, employees, customers, appointments, or events); the logged-in Amelia user must also not be a customer-role account for several read abilities.
Grouped by what each one can change. Every one starts off until you enable it.
Returns bookable services with their IDs, durations, and prices.
Returns providers/employees with the IDs needed by create-appointment and check-availability.
Returns customers with the IDs needed by create-appointment and book-event.
Returns events, classes, or group sessions with their IDs, periods, and capacity.
Returns existing appointments with their IDs, dates, and details.
Returns available booking datetimes for a service, grouped by date.
Creates a new bookable service with its name, duration, price, and assigned employees.
Registers a new customer with first name, last name, and email.
Books an appointment for a customer with a chosen service, employee, and date/time.
Creates a new event, class, or group session with a name, start/end time, price, and capacity.
Enrolls a customer into an existing event, class, or group session.
Cancels an existing appointment or event booking.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Amelia registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Amelia starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. Amelia registers all 12 of its booking abilities in the core Abilities API with explicit readonly/destructive annotations, so the Bridge can classify and expose each one directly.
Yes, unconditionally, once Amelia is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or newer with Amelia active. Each ability checks a dedicated Amelia capability or permission-service check for the entity and action involved (read or write access to services, employees, customers, appointments, or events); the logged-in Amelia user must also not be a customer-role account for several read abilities.
With the edit and delete toggles on, an agent can list, read, create, update, and delete bookings, customers, services, agents, locations, and orders, manage the booking calendar and off periods, read dashboard analytics, and read the activity log.
An agent can browse events, tickets, locations and bookings and read a specific booking's requirements, and can create or update events, tickets, locations, bookings, categories and tags, upload images for them, and change or delete bookings and other records when the connected user has the matching Events Manager capability.
Once enabled, an agent can read bookings, availability and event-type configuration, create, reschedule or cancel a booking on an attendee's behalf, pull scheduling reports, and run three guided prompts (daily briefing, event troubleshooting, weekly report); the scheduling toolset additionally lets it create and edit event types and availability schedules.
Verified from Amelia's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Melograno Venture Studio or Amelia. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.