Brevo (BYOK) — connector documentation
- MCP endpoint:
https://byok-brevo.connectorbay.com/mcp - REST API:
POST https://byok-brevo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-brevo.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Brevo API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-brevo.connectorbay.com/health· Tool schemas:https://byok-brevo.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-brevo · agent@connectorbay.com
What Brevo (BYOK) is for
Brevo (BYOK) lets an AI assistant read your own Brevo data through the Brevo API with a key you supply (API key). Read-only: 8 tools (get_account, list_contacts, list_contact_lists, list_segments, list_email_campaigns, get_email_campaign_report, list_senders, list_email_templates). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.brevo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brevo. Brevo and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Brevo account is my API key connected to and what plan is it on?"
- "Show my most recently added Brevo contacts"
- "What contact lists do I have in Brevo and how many subscribers are in each?"
- "Which segments exist in my Brevo account?"
- "How did my latest Brevo email campaigns perform?"
- "Give me the statistics of Brevo email campaign 12"
What it does
get_account: Show the Brevo account the key belongs to: organization, company name, login email, plan type and remaining credits.list_contacts: List contacts with email, blacklist flags, list memberships, dates and attributes. Newest first; can be filtered by list, segment or change date.list_contact_lists: List the contact lists in the account with their IDs, names and subscriber counts.list_segments: List the contact segments with their IDs, names, categories and last update time.list_email_campaigns: List email campaigns (newest first) with name, status, subject, send date and, for sent ones, the overall delivery, open and click statistics. This only reads campaigns; it never sends one.get_email_campaign_report: Get one email campaign's report: status, subject, send date and delivery, open, click, bounce and unsubscribe statistics, optionally per link, domain, device or browser. Read only.list_senders: List the sender identities (from name and email) with their IDs and whether each is active. Can filter by domain.list_email_templates: List transactional email templates with name, subject, sender, active flag and dates (the HTML body is not returned).
BYOK key
You bring your own Brevo API key (https://developers.brevo.com/docs/getting-started). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.brevo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://developers.brevo.com/reference (the API this connector calls, with a BYOK key)
Live from the Brevo API (api.brevo.com) with a BYOK key; documentation: https://developers.brevo.com/reference. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brevo. Brevo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Brevo account.
Built for: Worldwide. Languages: English.