The Brevo MCP server is the official integration for Brevo’s email and CRM platform. It covers contacts and lists, campaigns and their performance, and the CRM records alongside them, which makes it useful for the reporting and hygiene work that otherwise sits untouched.
What it actually does
The server authenticates with an API key and exposes Brevo’s objects as tools. The agent can read contacts and list membership, pull campaigns with their open, click and bounce statistics, and access CRM records. With broader scopes it can create and modify, including operations that result in email being sent.
Practical patterns:
- ‘Which contacts have not opened anything in six months?’
- ‘Compare this month’s campaigns against last month and explain the difference in click rate.’
- ‘How many contacts are on more than one list, and which lists overlap most?‘
Why use it
List hygiene is the classic never-done task. Deliverability degrades quietly as unengaged contacts accumulate, and the work of identifying them is a series of exports and filters. An agent can answer it directly. Campaign comparison is the other: the data to work out what actually drives opens exists in every account and almost nobody assembles it.
Gotchas
Anything that sends should stay behind a person. That covers campaign sends and transactional triggers, both of which are irreversible and visible to customers. Contact deletion is similarly one-way, so let the agent produce the list and do the removal yourself. Scope the API key to what the task needs rather than granting everything, and remember that contact data is personal data flowing to your AI provider.
