An agent can generate a click-to-chat WhatsApp URL and read or update the configured phone number, call-to-action text, and pre-filled message, globally or for a specific post or term.
2 read3 destructive
View abilitiesNotificationX abilities, governed through the Bridge
Once its MCP module is enabled, an agent can list, inspect, create, update, toggle, duplicate and delete FOMO/social-proof notifications, describe a notification type's valid sources and themes, and read form entries, analytics and plugin settings.
- Abilities
- 1515 destructive
- Active installs
- 30K+
- Rating
- 96% (227 ratings)
- Version
- 3.3.2
- Requires
- WP 5.0+, PHP 5.6+
- Last updated
- 2026-09-24
View NotificationX on WordPress.org
What has to be true first
Needs NotificationX's MCP module enabled and WordPress 6.9 or later. Every ability checks manage_options; none override the base class's capability.
- NotificationX's own MCP module must be turned on (Settings > MCP, off by default); enabling it calls boot(), which is what registers the abilities into both NotificationX's own registry and the core Abilities API.
The 15 NotificationX abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive 15
- Destructive
List notifications
Lists campaigns with their type, data source, theme, and active status, with optional filters.
- Destructive
Get notification
Reads one notification's full configuration.
- Destructive
List notification types
Lists the notification types available (e.g. conversions, reviews).
- Destructive
List data sources
Lists the data sources notifications can pull from (e.g. WooCommerce, comments).
- Destructive
Describe a notification type
Returns a type's valid data sources, theme ids, and content-template placeholders, for use before creating or updating a notification.
- Destructive
Get status
Reads plugin/module status.
- Destructive
Get analytics
Reads notification analytics such as views and conversions.
- Destructive
Get settings
Reads plugin settings.
- Destructive
List form entries
Lists form/notification entries.
- Destructive
Export form entries (CSV)
Exports form/notification entries as CSV.
- Destructive
Create a notification
Creates a new notification.
- Destructive
Enable or disable a notification
Enables or disables a notification.
- Destructive
Update a notification
Updates a notification's configuration.
- Destructive
Duplicate a notification
Duplicates an existing notification.
- Destructive
Delete a notification
Deletes a notification.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install NotificationX and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. NotificationX registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
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.
Enable one ability at a time
Every ability from NotificationX starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
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.
Frequently asked questions
Does NotificationX work with the Bridge?
Conditionally. NotificationX mirrors its 15 abilities into the core Abilities API only after its own MCP module boots, and its shared annotations() method emits MCP-style keys (readOnlyHint, destructiveHint, idempotentHint) rather than the Abilities API's own readonly/destructive keys, so under the Bridge's fail-safe rule every one of them, including the 10 read abilities, classifies as destructive.
What has to be true for NotificationX's abilities to register?
NotificationX's own MCP module must be turned on (Settings > MCP, off by default); enabling it calls boot(), which is what registers the abilities into both NotificationX's own registry and the core Abilities API..
Does NotificationX need anything special to work with the Bridge?
Needs NotificationX's MCP module enabled and WordPress 6.9 or later. Every ability checks manage_options; none override the base class's capability.
More Marketing plugins
PixelYourSite
ConditionalAn agent can audit which tracking pixels (Facebook, GA4, GTM, Bing, Pinterest, Reddit) are configured and healthy, read WooCommerce and Easy Digital Downloads event mappings, and, when the plugin's read-only toggle is off, create or update custom tracking events and automatic-event triggers.
10 read5 destructive
View abilitiesAn agent can list, create, update and delete short links and their categories or tags, check whether a slug is free, and pull click analytics and audience breakdowns, or delete stored analytics and change plugin settings.
10 read2 write6 destructive
View abilitiesVerified from NotificationX'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, WPDeveloper or NotificationX. Back to the full directory.
Bridge NotificationX, keep the same control.
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.