An AI agent can browse the event calendar (events, tickets, venues, performers, organizers, event types), check ticket availability, create a booking, look up or cancel a booking, create or update events and taxonomy-like entries, export attendee lists, and update a user's stored timezone.
View EventPrime on WordPress.org
EventPrime needs to be installed and active on WordPress 6.9 or later. Reading events, tickets, venues, performers, organizers and event types is left open to any caller (allow_public_access), while creating, updating, deleting or canceling content checks event-specific capabilities such as edit_em_event, delete_em_event or manage_em_event_terms, falling back to manage_options.
Grouped by what each one can change. Every one starts off until you enable it.
Lists events on the calendar.
Returns one event's detail.
Lists tickets for an event.
Checks remaining ticket availability for an event.
Returns one booking's detail.
Lists event venues.
Lists event performers.
Lists event organizers.
Lists event types.
Exports the attendee list for an event.
Creates a new event.
Updates an existing event.
Creates a new event booking.
Cancels an existing booking.
Creates a new venue.
Creates a new performer.
Creates a new organizer.
Creates a new event type.
Updates the connected user's stored timezone preference.
Deletes an event.
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. EventPrime 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 EventPrime 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. One class registers all 20 abilities with wp_register_ability under the eventprime-content-management category, each with its own permission_callback, so all of them are individually switchable once the operator enables the Bridge.
Yes, unconditionally, once EventPrime is active. Nothing else has to be configured for the Bridge to discover them.
EventPrime needs to be installed and active on WordPress 6.9 or later. Reading events, tickets, venues, performers, organizers and event types is left open to any caller (allow_public_access), while creating, updating, deleting or canceling content checks event-specific capabilities such as edit_em_event, delete_em_event or manage_em_event_terms, falling back to manage_options.
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.
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.
Verified from EventPrime'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, Metagauss or EventPrime. 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.