Brevo MCP server
Brevo is an email and SMS marketing platform that businesses use to manage contacts, send campaigns, and track engagement alongside basic CRM records. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Brevo.
Get contact status
Use when checking one known contact by its exact numeric ID before a consent-sensitive change. Returns only structural status and list membership, without personal attributes. Missing contacts return provider_not_found.
Create contact
Use when creating a new contact whose documented consent the caller already holds. This call neither records nor sends consent. No upsert, merge or list addition. Do not recreate unsubscribed contacts. No direct email; read back before retrying an uncertain result.
Update contact safely
Use when editing default FIRSTNAME/LASTNAME attributes, blocking email, or removing list memberships. Blocking cannot be undone through this connector. Never changes email or reverses opt-outs. No direct email; automations may react. Read back before retrying an uncertain result.
8 Brevo actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
4Look things up, subject to your permissions.
- brevo.get_contactGet contact status
Use when checking one known contact by its exact numeric ID before a consent-sensitive change. Returns only structural status and list membership, without personal attributes. Missing contacts return provider_not_found.
- brevo.list_contact_listsList contact lists
Use when discovering list IDs and folders before an approved membership change. Returns one bounded page of list metadata, never the contacts themselves. Count is account-wide, not the number returned on this page.
- brevo.list_email_campaignsList email campaigns
Use when discovering campaign IDs for reporting. Returns one bounded page of names and statuses without message content or recipient details. Does not send campaigns.
- brevo.get_campaign_reportGet campaign report
Use when measuring delivery and engagement for a known campaign ID. Returns aggregate statistics only; null metrics mean unavailable, not zero. No recipient data, email content, or report email is returned or sent.
write
3Create and change things. Allow, or ask the user first.
- brevo.create_contactCreate contact
Use when creating a new contact whose documented consent the caller already holds. This call neither records nor sends consent. No upsert, merge or list addition. Do not recreate unsubscribed contacts. No direct email; read back before retrying an uncertain result.
- brevo.add_contact_to_listAdd contact to list
Use when the caller already holds documented consent for this list; this call neither records nor sends consent. Blocks any group opt-out conservatively. List automations may email this contact. Never resubscribe; read back before uncertain retries and inspect failure IDs.
- brevo.send_transactional_emailSend transactional email
Use when authorized to send transactional email now; consumes credits. Same idempotencyKey maps to the same UUID (30-minute deduplication). duplicate_parameter means an earlier attempt with this key was accepted; read back delivery status before retrying with a new idempotencyKey.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- brevo.update_contactUpdate contact safely
Use when editing default FIRSTNAME/LASTNAME attributes, blocking email, or removing list memberships. Blocking cannot be undone through this connector. Never changes email or reverses opt-outs. No direct email; automations may react. Read back before retrying an uncertain result.
Control access to Brevo.
Connect the intended Brevo account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- brevo.create_contact: require approval
- brevo.update_contact: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Brevo connects.
Connect Brevo using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Brevo with your AI client.
Sign in to Arc0 and connect Brevo in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Brevo with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingBrevo with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingBrevo with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingBrevo with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingBrevo with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingBrevo with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Brevo and Arc0, answered.
Does Brevo work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Brevo with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Brevo MCP server?
This is Arc0’s integration page, not a claim of an official Brevo server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Brevo for its own current MCP offerings.
Which Brevo actions are supported?
8 registry-defined actions: 4 read, 3 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Brevo need?
Connect Brevo using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Brevo?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Brevo through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Brevo into your agent.
Brevo MCP server: 8 actions including get contact status, create contact, update contact safely. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Brevo and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Brevo.