Brevo MCP integration for AI agents.
Connect AI agents to Brevo through 12 structured actions, including add contacts to list, create contact, and delete contact. Review authentication, inputs…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Brevo integration exposes
The Brevo Agent App exposes 12 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent add contacts to one brevo contact list using exactly one official selector, create one brevo contact with the official contact creation payload, and delete one brevo contact by identifier and optional identifier type. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Brevo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Brevo capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_contacts_to_listREADAdd contacts to one Brevo contact list using exactly one official selector.
create_contactWRITECreate one Brevo contact with the official contact creation payload.
INPUTS: email / extId / listIds / emailBlacklisted / smsBlacklisted
delete_contactHIGH IMPACTDelete one Brevo contact by identifier and optional identifier type.
INPUTS: identifier / identifierType
create_contact_listREADCreate one Brevo contact list inside the specified Brevo folder.
INPUTS: name / folderId
get_accountREADRetrieve the current Brevo account profile and plan information.
get_contactREADRetrieve one Brevo contact by identifier and optional identifier type.
INPUTS: identifier / identifierType
list_contact_foldersREADList Brevo contact folders with the official pagination parameters.
INPUTS: limit / offset / sort
list_contact_listsREADList Brevo contact lists with the official pagination parameters.
INPUTS: limit / offset / sort
list_contactsREADList Brevo contacts with pagination and timestamp filters.
INPUTS: limit / offset / sort / modifiedSince / createdSince
list_contacts_in_listREADList the Brevo contacts currently linked to one Brevo contact list.
INPUTS: listId / limit / offset / sort / modifiedSince
remove_contacts_from_listHIGH IMPACTRemove contacts from one Brevo contact list using exactly one official selector.
update_contact_listREADUpdate one Brevo contact list by ID.
INPUTS: listId / name / folderId
INPUT CONTRACTS
Know what the action needs before it runs.
create_contact
emailREQUIRED- The email address for the new contact.
extIdOPTIONAL- The optional external identifier attached to the contact.
listIdsOPTIONAL- The non-empty positive integer array accepted by Brevo.
emailBlacklistedOPTIONAL- Whether the contact should be email blacklisted.
smsBlacklistedOPTIONAL- Whether the contact should be SMS blacklisted.
delete_contact
identifierREQUIRED- The Brevo contact identifier value used in the request path.
identifierTypeOPTIONAL- The optional Brevo identifier type used to interpret the identifier.
create_contact_list
nameREQUIRED- The Brevo contact list name.
folderIdREQUIRED- The Brevo folder ID.
get_contact
identifierREQUIRED- The Brevo contact identifier value used in the request path.
identifierTypeOPTIONAL- The optional Brevo identifier type used to interpret the identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add Contacts To List
Add contacts to one Brevo contact list using exactly one official selector. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_contacts_to_listControl Create Contact
Create one Brevo contact with the official contact creation payload. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Create Contact List
Create one Brevo contact list inside the specified Brevo folder. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_contact_listSAFETY BOUNDARY
Operate Brevo with explicit limits
- Authorize Brevo with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` and `remove_contacts_from_list` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Brevo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Brevo task completed successfully.
CONNECTION MODEL
API key
Brevo API key sent with the api-key header. Create or copy API keys in Brevo under SMTP & API > API Keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Brevo.