Skip to content
Custom Connectors

Full read-write Claude connector for Brevo

Let Claude update contacts, manage lists, and queue sends in Brevo

Stop switching tabs to clean up contacts and prep campaigns by hand. Claude updates contacts, moves them between lists, drafts the email, and queues the send right inside Brevo, where your audience already lives, with the actual send held until you approve it.

Brevo is an email, SMS, and marketing automation platform that teams use to run campaigns and manage contacts. People want Claude to do more than read campaign stats: to update contacts, build lists, and queue sends from inside the conversation.

What is a Brevo MCP server?

A Brevo MCP server is a small hosted service that exposes Brevo's data and actions to Claude over the Model Context Protocol, so Claude can campaigns, lists, and audiences inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Brevo's current connector do today?

Brevo ships an official native Claude connector, but it exposes a fixed, standard set of tools that covers a generic slice of the platform. A custom connector delivers the full capabilities your workflow needs: the specific contact actions, attribute and list logic, campaign prep, scoping, and human-in-the-loop control its built-in tool set leaves out.

What does full read-write Brevo access unlock?

Full read-write Brevo access lets Claude create and update contacts, move them between lists, edit contact attributes, draft a campaign or transactional message, and queue a send once you approve. The list hygiene and campaign prep that used to mean switching tabs happen where your contacts already live.

  • Create or update a contact and set its attributes
  • Add or remove contacts from a list or segment
  • Draft an email campaign and save it for review
  • Queue a transactional or campaign send after you approve
  • Tag and re-segment contacts based on a query you describe
  • Update an existing contact's email preferences or unsubscribe status

Can Claude update contacts in Brevo?

Yes. With a full read-write Brevo connector, Claude can update contacts: create new ones, edit attributes, change email preferences, and update unsubscribe status. A read-only setup over the Brevo API can only fetch contacts and reports, so these write actions need a connector with the right permissions enabled.

Can Claude manage list membership and segments in Brevo?

Managing list membership is something Claude can do: it adds or removes contacts from a list, tags and re-segments based on a query you describe, and edits contact attributes. The work happens inside Brevo, so list hygiene no longer means exporting, editing a spreadsheet, and re-importing.

Will Claude send a Brevo campaign without my approval?

No. Claude can draft an email campaign or a transactional message and save it for review, but the actual send is a separate, gated action that runs only after you approve it. Drafting and re-segmenting flow freely while the outbound send always waits for a human.

How a Brevo connector works

We build a small MCP server that connects to Brevo with a scoped API key, requesting only the permissions the work needs. Read tools (fetch contacts, lists, campaign reports) and write tools (create contact, edit list, queue send) are separated, and outbound or destructive actions like sending a campaign or deleting a contact require your confirmation. Claude never gets more access than the API key itself carries, and we can IP allowlist the server where Brevo supports it.

Frequently asked questions

Can Claude actually update contacts in Brevo, not just read them?
Yes. Brevo's native connector ships a fixed, generic tool set, so the specific contact and list actions your workflow needs are not always shaped the way you want. A custom Brevo connector exposes the exact write tools for creating and updating contacts, editing attributes, and changing list membership, with the right scoped permissions enabled.
Will Claude send a Brevo campaign without my approval?
No. Sending is a separate, gated write action. Claude can draft a campaign or prepare a transactional message, but the actual send only happens after you approve it. You decide which actions run automatically and which require a confirmation step, so a send never goes out unexpectedly.
Does the connector get more access to Brevo than my API key?
No. The connector uses a Brevo API key that you scope, and it inherits only the permissions that key carries. If the key cannot delete contacts or send campaigns, neither can Claude. You can rotate or revoke the key at any time, and we can IP allowlist the server where Brevo supports it.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.