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.
View Fluent Booking on WordPress.org
FluentBooking needs WordPress 6.9 and its own MCP setting turned on in Settings, since abilities are not registered until that switch is on. Read abilities need only a FluentBooking permission of any kind; booking-write abilities need manage_own_calendar, manage_all_bookings, or manage_all_data; scheduling-write abilities need manage_own_calendar, manage_other_calendars, manage_other_availabilities, or manage_all_data. FluentBooking's own privacy-policy text warns that a connected client can read attendee names, emails, phone numbers and booking answers within that WordPress user's permissions.
Source defines 16 distinct ability ids across both toolsets (9 core tools, 3 core prompts, 4 scheduling tools); easymcp lists 13, closest to the core toolset alone (12) plus one, so it likely undercounts the always-on prompt or scheduling abilities.
Grouped by what each one can change. Every one starts off until you enable it.
Read cached reference context (event types, statuses, periods) used to build other queries.
List bookings with filters, returning a compact masked row per booking.
Read one booking in full.
Read the open booking slots for an event type.
Read a diagnostic breakdown of why an event type shows the slots it does.
List the site's configured event types.
Run a scheduling report query across bookings.
Read a host's configured availability schedule.
Read reference lists used to configure scheduling (timezones, locations, and similar lookups).
Create a new booking on an attendee's behalf.
Reschedule, cancel, or otherwise change an existing booking.
Summarize a day's schedule: what is booked, what needs a decision, and what changed.
Work out why an event type is showing no slots, or the wrong ones, and say what to change.
Produce a week's booking numbers with comparison and caveats.
Create or edit an availability schedule.
Create or edit an event type's configuration.
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. Fluent Booking 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 Fluent Booking 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.
Conditionally. FluentBooking's MCP module wires wp_register_ability only when the operator has switched on its own MCP setting (PermissionGate::isEnabled(), off by default): until then the hooks that call AbilitiesRegistrar::register() are never attached, so the bridge sees nothing for this plugin.
The operator must turn on FluentBooking's own 'MCP for AI Agents' toggle in its settings, which is off by default. Abilities register per enabled toolset: the Core toolset (bookings, event types, reports, context, and three prompt abilities) is always on once MCP is enabled, the Scheduling toolset (availability and event-type write abilities) is a separate opt-in switch, and a Payments toolset exists only in the paid Pro add-on.
FluentBooking needs WordPress 6.9 and its own MCP setting turned on in Settings, since abilities are not registered until that switch is on. Read abilities need only a FluentBooking permission of any kind; booking-write abilities need manage_own_calendar, manage_all_bookings, or manage_all_data; scheduling-write abilities need manage_own_calendar, manage_other_calendars, manage_other_availabilities, or manage_all_data. FluentBooking's own privacy-policy text warns that a connected client can read attendee names, emails, phone numbers and booking answers within that WordPress user's permissions.
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 Fluent Booking'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, WPManageNinja or Fluent Booking. 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.