Brevo MCP and Linkeddit in Claude: which Brevo server to use, and how to draft competitor-led campaigns

Brevo documents two routes into Claude. The Claude connector is listed in Claude's directory, signs in with OAuth and, per the Agent Index, has 21 tools: 16 reads and 5 writes. Brevo's help center says Claude can create email campaign, SMS campaign and template drafts, and that it cannot send, schedule or delete anything.

The Brevo MCP server is the developer route. Brevo's documentation says to generate an MCP token in your account, then connect to https://mcp.brevo.com/v1/brevo/mcp, which combines 27 modules, or to a single module such as contacts or campaign analytics. Audienceful, a competitor of Brevo, counts 193 tools and says it can send campaigns and is in early access. That tool count and the sending claim come from Audienceful, not from Brevo's page, so check them against your own account before you rely on them.

For competitor-led campaigns, the draft-only connector is usually the right start: the data tells you what to say, and you press send yourself in Brevo.

Brevo knows your own account: campaigns, results, contacts, lists and segments. It knows nothing about what a competitor changed this week or where the answer engines name them instead of you. Linkeddit supplies that outside view, as data. Both come to Claude, which writes the draft.

On Linkeddit's test project, plausible.io, the competitor signals feed returned 19 items for the week of 2026-10-26. One was marked high priority: Fathom Analytics launched an AI assistant called Luna. The Answer Radar gap list held one open gap, ranked first: the project is not represented for the question Umami vs Matomo for self-hosted analytics. That is a real subject for an email, and Linkeddit wrote none of it. Linkeddit is one plan at $60 a month.

The need is plain in how people describe email tools. "Just as I feared, I have to be a rocket scientist just to email to list of subscribers," wrote a viewer on a Brevo beginner tutorial on YouTube. Asking for a draft in plain language, from a named list, removes most of that.

Brevo's own best practice points the same way. Its help center advises naming a time range and the list or segment you want to target, and reviewing every draft in Brevo before it is sent.

Run one saved prompt each week. Claude reads the week's competitor signals and AI answer gaps from Linkeddit, reads your last campaigns from Brevo, then saves an email campaign draft addressed to a list you name. In the test run, the digest would lead with Fathom's Luna launch, then Matomo's security update, which Linkeddit graded high priority.

Claude works when you start it, so this is a routine you trigger, not a scheduled send. Linkeddit keeps its data fresh between runs, with competitor monitors that run weekly. Brevo's connector will not schedule or send, so the final step stays with you.

Start from the signal, not the reaction. Ask Linkeddit for the competitor's change with its date and source link, ask Brevo which past campaigns your audience opened, then have Claude draft one email that states your position without naming the competitor's price as fact unless the source says it.

Check every claim before it goes. A signal carries a source_url and a why_it_matters line, so you can open the competitor's page and confirm. Several signals on the test project had no signal_date at all, which is a reason to read the source, not trust the summary.

Yes, as a draft. Comparison content is the case where AI answers matter most: when the engines recommend a rival for a question like Umami vs Matomo for self-hosted analytics, a campaign and a page that answer it plainly give your audience and the engines something of yours to quote.

Ask Claude to pull the gap and its question from Linkeddit, check the claims against your own product facts, and save one template or campaign draft in Brevo. Linkeddit measures the gap; the comparison itself is written by Claude and approved by you.

Brevo lists one known limitation: the connector does not take user permissions into account, because it grants access through the MCP key, whatever role the person has in Brevo. Brevo's advice is to share access only with users you trust.

The same help center says Claude can occasionally produce inaccurate results and asks you to review output, so ask Claude to cite the exact Brevo data behind each statement. Disconnecting the connector in Claude's Connectors page removes its access at once and leaves your Brevo data unchanged.