Choose the Brevo job before the operation
The right path depends on what must change next.
Change audience data
Choose this path when a contact, its attributes, or the lists and folders that organize it must change.
Route contacts by language
Choose this path when language determines which audience should receive a contact.
Connect a customer touchpoint
Choose this path when the next interaction is a campaign, email, signup form, webhook, sender, template, or localized prompt.
Three conditions keep a Brevo result usable
A useful operation needs a clear permission, a configured connection, and an answer worth inspecting.
01
Permission
The authenticated WordPress user must have the manage_options capability; every Brevo ability checks that administrative scope before it runs.
02
Connection
The official Brevo for WordPress integration supplies the site’s Brevo connection.
03
Inspectable result
A structured response gives the operator something concrete to inspect after the request.
Find the operation that matches the work
Each row names a reader outcome and the exact WordPress abilities behind it.
Verify the account and request
Inspect the connected account with brevo/get-account. For a targeted Brevo v3 request, use brevo/api-request with a relative endpoint; external absolute endpoints are rejected. Every Brevo ability requires the WordPress manage_options capability, and remote requests require an API key configured through Brevo for WordPress. The released plugin is distributed through the stable self-hosted ZIP, and each call returns structured results for verification.
Contacts and attributes
Inspect one contact with brevo/get-contact or review the set with brevo/list-contacts. Create, update, or delete records with brevo/create-contact, brevo/update-contact, or brevo/delete-contact. For the fields that describe those records, list, create, update, or delete attributes with brevo/list-attributes, brevo/create-attribute, brevo/update-attribute, or brevo/delete-attribute.
Lists, folders, and language audiences
Inspect folders and lists with brevo/get-folder, brevo/list-folders, brevo/get-list, and brevo/list-lists. Create, update, or delete folders with brevo/create-folder, brevo/update-folder, or brevo/delete-folder. Create, update, or delete lists with brevo/create-list, brevo/update-list, or brevo/delete-list, then add or remove contacts with brevo/add-to-list and brevo/remove-from-list. For language-based membership, list audiences with brevo/list-language-audiences, ensure them with brevo/ensure-language-audiences, and place a contact in the matching audience with brevo/upsert-language-contact.
Campaigns, senders, and email
List campaigns with brevo/list-campaigns and send them with brevo/send-campaign. List and inspect templates with brevo/list-templates and brevo/get-template. Inspect sender domains and senders with brevo/list-sender-domains and brevo/list-senders, create a sender with brevo/create-sender, and send transactional email with brevo/send-email.
Forms and webhooks
For signup forms stored by the official Brevo WordPress plugin, list with brevo/list-wordpress-forms, inspect with brevo/get-wordpress-form, create with brevo/create-wordpress-form, update with brevo/update-wordpress-form, delete with brevo/delete-wordpress-form, or ensure with brevo/ensure-wordpress-form. For Brevo webhooks, list with brevo/list-webhooks, inspect with brevo/get-webhook, create with brevo/create-webhook, update with brevo/update-webhook, or delete with brevo/delete-webhook.
WonderPush localization
Inspect the WordPress-stored WonderPush prompt and widget localization with brevo/wonderpush-get-localization, update it with brevo/wonderpush-update-localization, and audit it with brevo/wonderpush-audit-localization.
What the WordPress connection needs
These named dependencies provide the runtime, ability registration, MCP connection, and Brevo integration.
Required through WordPress 6.9 or newer
WordPress Abilities APIRegisters, describes, validates, and permission-checks the abilities exposed by MCP Abilities – Brevo.
Required; PHP 8.0 or newer
PHP 8.0Provides the server runtime required by MCP Abilities – Brevo.
Required to expose registered abilities as MCP tools; activation required
WordPress MCP AdapterExposes registered WordPress abilities to MCP clients.
Required for forms and the API key; leave this integration enabled
Brevo for WordPressProvides the stored signup forms and the API key used for Brevo account, audience, delivery, and webhook operations.
Download the stable package
Download the stable self-hosted ZIP to obtain the MCP Abilities – Brevo package for the WordPress site. The connected AI client can then use its registered Brevo operations.