An agent can list, search, and read events, calendars, and tags, pull aggregate event counts, and create or update individual events, calendars, and tags.
View Sugar Calendar on WordPress.org
Sugar Calendar and WordPress 6.9 or later must both be active for these abilities to appear in the registry. Read abilities require edit_posts or the plugin's manage_event_calendars capability; the four write abilities require create_events, an edit_post check on the specific event, or the calendar/tag taxonomy's own edit_terms capability.
The easymcp count of 6 covers only the read abilities; the plugin also registers 4 write abilities (create/update event, create calendar, create tag) whose mcp.public flag is false, plus get-event-stats, for 12 in the free plugin.
Grouped by what each one can change. Every one starts off until you enable it.
Lists events, optionally filtered by date range or calendar.
Reads a single event's details.
Full text searches events by title or content.
Lists the site's calendars.
Reads a single calendar's details.
Lists the event tags in use.
Reads a single event tag's details.
Returns aggregate counts of events, such as totals by status or time range.
Creates a new event.
Edits an existing event.
Creates a new calendar, or returns the existing one if the name already exists.
Creates a new event tag, or returns the existing one if the name already exists.
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. Sugar Calendar 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 Sugar Calendar 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. It registers 12 abilities under the sc-events namespace with real annotations and per-ability permission callbacks, so the Bridge can list and switch on each one.
A thirteenth ability, sc-events/get-registration-stats, only registers when the separate Event Ticketing or RSVP add-on is active and contributes a signup mode; it is absent in the free plugin alone. Four of the twelve abilities (create-event, update-event, create-calendar, create-tag) set mcp.public to false, so a connector that only lists publicly exposed abilities will not surface them even though they are registered.
Sugar Calendar and WordPress 6.9 or later must both be active for these abilities to appear in the registry. Read abilities require edit_posts or the plugin's manage_event_calendars capability; the four write abilities require create_events, an edit_post check on the specific event, or the calendar/tag taxonomy's own edit_terms capability.
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 Sugar Calendar'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, Syed Balkhi or Sugar Calendar. 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.