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.
View Events Manager on WordPress.org
Events Manager must be installed and active on WordPress 6.9 or newer for the Abilities API (the plugin readme lists a lower floor of 6.1, which covers Events Manager's other features). Most read abilities are open to any visitor, booking reads require a logged-in user, and the write and destructive abilities are gated by Events Manager's own edit_events, manage_bookings, edit_locations, and similar capabilities, which the connected WordPress user must hold.
Matches easymcpai's listed count of 38. Ability IDs are constructed at runtime in em-api-abilities.php: register_ability() prepends 'events-manager/' to the passed slug, and register_term_abilities() generates the 10 category/tag abilities from a factory pattern. Evidence shows source code, not literal IDs. These ability names are put together by the plugin's code when it registers them, so we worked them out from that code. Check the exact names on your site's Bridge screen.
Grouped by what each one can change. Every one starts off until you enable it.
Retrieves a filtered collection of events.
Retrieves one event by ID.
Retrieves booking availability, spaces, and ticket availability for one event.
Returns the fields, payment options, and an example payload needed to book one event.
Retrieves the tickets for one event.
Retrieves one ticket by ID.
Retrieves a filtered collection of locations.
Returns countries usable in a location picker, optionally narrowed to those with a stored location.
Returns the distinct region names present in stored locations.
Returns the distinct state or province names present in stored locations.
Returns the distinct town or city names present in stored locations.
Retrieves one location by ID.
Retrieves the bookings visible to the current user.
Retrieves one booking by ID if visible to the current user.
Retrieves event categories.
Retrieves one event category by ID.
Retrieves event tags.
Retrieves one event tag by ID.
Creates a new event.
Creates a ticket for an event.
Creates a new venue location.
Uploads or sideloads an image into the media library, optionally as an event or location featured image.
Creates a booking for an event.
Creates a new event category.
Creates a new event tag.
Updates an existing event.
Deletes or trashes an event.
Updates an existing ticket.
Deletes a ticket that has no bookings.
Updates an existing venue location.
Deletes or trashes a venue location.
Updates an existing booking.
Changes a booking's status, such as approving, rejecting, or cancelling it.
Permanently deletes a booking.
Updates an existing event category.
Deletes an event category.
Updates an existing event tag.
Deletes an event tag.
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. Events Manager 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 Events Manager 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. Events Manager registers 38 abilities across events, tickets, locations, bookings, categories and tags with per-ability capability checks, so the Bridge can wrap and expose each one once an operator turns it on; the plugin also ships its own separate MCP server file, but that does not block bridging since the abilities are registered independently through the core Abilities API.
Yes, unconditionally, once Events Manager is active. Nothing else has to be configured for the Bridge to discover them.
Events Manager must be installed and active on WordPress 6.9 or newer for the Abilities API (the plugin readme lists a lower floor of 6.1, which covers Events Manager's other features). Most read abilities are open to any visitor, booking reads require a logged-in user, and the write and destructive abilities are gated by Events Manager's own edit_events, manage_bookings, edit_locations, and similar capabilities, which the connected WordPress user must hold.
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 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.
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 Events Manager'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, Marcus (aka @msykes) or Events Manager. 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.