> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://developers.brevo.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.brevo.com/_mcp/server. # Brevo skills ## Overview A skill is a short set of instructions (a `SKILL.md` file) that teaches an AI agent how to do one job well. Brevo skills cover jobs such as writing and checking an email, creating a campaign draft, sending a test, reading an account's brand kit, or driving the Brevo Developer CLI. Skills contain text only. They never hold an API key and never call an API directly. The email skills act on your account through the [Brevo MCP server](./mcp-protocol), which signs you in with OAuth, so there is nothing to copy or paste. The `brevo-cli` skill instead drives the [Brevo Developer CLI](/docs/cli-reference) from your shell, using the CLI's own login. The skills are published at [getbrevo/brevo-skills](https://github.com/getbrevo/brevo-skills) and work with Claude, ChatGPT, Codex, Gemini, Cursor and any agent that reads `SKILL.md`. Anyone can browse, copy or fork the repository. You can get them in six ways: * **Plugin:** Claude Code, Codex, Gemini CLI, Cursor and Grok read the repository directly. ChatGPT has a published [Brevo plugin](https://openai.com/business/plugins/brevo/). * **Brevo CLI:** `brevo skill install` copies skills to your agent and checks every file against a hash. * **`npx skills add`:** works with any agent that reads `SKILL.md`. * **ZIP upload:** for claude.ai, ChatGPT and the Gemini app, which have no git. * **Brevo MCP server:** agents that can't install anything load the skills through `get_brevo_guide`. * **Public repository:** copy a skill by hand. ## Available skills | Skill | What it does | Status | Needs | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------ | -------------------- | | `brevo-guide` | Loads any Brevo skill through the Brevo MCP server, and says where to install the skills | Beta | The Brevo MCP server | | `email` | Entry point for email work: confirms the account, splits the request into steps and names the skill for each | Beta | The Brevo MCP server | | `email-template-write` | Writes the HTML of a campaign, automation or transactional email, with personalization | Beta | The Brevo MCP server | | `email-template-check` | Checks email HTML against Brevo's template rules and fixes what fails | Beta | The Brevo MCP server | | `email-template-to-dnd` | Turns email HTML into a design that opens in the drag-and-drop editor, and saves it as a template | Beta | The Brevo MCP server | | `email-campaign-create` | Creates a campaign as a draft from finished HTML, for a list and a verified sender. Never sends | Beta | The Brevo MCP server | | `email-test-preview` | Previews a draft email and sends a test to the addresses you choose | Beta | The Brevo MCP server | | `email-brand-kit` | Reads your account's brand kit (logo, colours, fonts, social links) as email styles, and sets it up or changes it after you approve | Beta | The Brevo MCP server | | `brevo-cli` | Uses the [Brevo Developer CLI](/docs/cli-reference) to manage OAuth apps, UI apps and Brevo Functions | Public | A shell and the CLI | The email skills work together: `email` routes a request to the others, and nothing is sent to real recipients without your explicit yes. The full list and each skill's version are in the [catalog](https://github.com/getbrevo/brevo-skills/blob/main/catalog.json). ## Install #### Claude Code ```bash /plugin marketplace add getbrevo/brevo-skills /plugin install brevo@brevo-skills ``` The plugin adds the skills and the Brevo MCP server together. #### Codex ```bash codex plugin marketplace add getbrevo/brevo-skills ``` Then open `/plugins` and install **brevo**. #### Gemini CLI ```bash gemini extensions install https://github.com/getbrevo/brevo-skills ``` #### Cursor In Cursor's plugin settings, add the plugin from `getbrevo/brevo-skills`. #### Brevo CLI With a shell and Node.js, the [Brevo CLI](/docs/cli-reference) (v2.6.0 or later) installs the skills on disk, where your agent reads them: ```bash npm i -g @getbrevo/cli brevo skill list brevo skill install ``` Install one skill, or choose the agent to install for: ```bash brevo skill install email-test-preview --agent claude ``` Add `--dry-run` to see what would change first, and `--mcp` to register the Brevo MCP server with your agent in the same step. Keep skills current with `brevo skill update`, and check for newer versions with `brevo skill check`. #### Any other agent ```bash npx skills add getbrevo/brevo-skills ``` This installs the skills only. Connect the [Brevo MCP server](./mcp-protocol) separately. #### ChatGPT Add the [Brevo plugin](https://openai.com/business/plugins/brevo/). It connects ChatGPT to your Brevo account through the Brevo MCP server and bundles Brevo skills, so you can ask, for example, "What's the open and click rate on my last email campaign in Brevo?" Skills inside a plugin work on web, desktop and mobile. A skill you upload yourself as a ZIP works in the desktop app. Plan availability differs by tier. #### claude.ai, Gemini app Download the skill ZIP from the [latest release](https://github.com/getbrevo/brevo-skills/releases) and upload it in your agent's skill settings: in claude.ai, Customize, then Skills, then Upload a skill. Add the Brevo connector separately. For Claude, use the [Brevo connector](https://claude.com/marketplace/connectors/brevo) from Claude's directory. Skills that need a shell, such as `brevo-cli`, are not available in chat apps. Uploads don't update themselves: download the new ZIP and upload it again. Also supported: Claude Cowork (add the marketplace `getbrevo/brevo-skills` under Plugins), Grok (install the plugin from `getbrevo/brevo-skills`), Antigravity CLI (`agy plugin install` with the Antigravity ZIP from a release), Gemini Enterprise (import the skill ZIP) and the OpenAI Responses API (upload the skill ZIP to `/v1/skills`). > **Note** > > Each platform has its own limits on what it accepts. The [platform guide](https://github.com/getbrevo/brevo-skills/blob/main/docs/platforms.md) lists every install path, what each one includes and the known limits. Use the plugin or the Brevo CLI for a given agent, not both, or the agent sees each skill twice. ## Connect the Brevo MCP server The email skills need the Brevo MCP server to act on your account (`brevo-cli` uses the CLI instead). The plugins above add it for you. For anything else, connect the endpoint for your platform and sign in with OAuth when your agent asks: | Platform | MCP endpoint | Used by | | -------- | ---------------------------------------- | --------------------------------------- | | Claude | `https://mcp.brevo.com/v1/anthropic/mcp` | Claude Code, claude.ai, Desktop, Cowork | | OpenAI | `https://mcp.brevo.com/v1/openai/mcp` | ChatGPT, Codex, Cursor, Grok | | Gemini | `https://mcp.brevo.com/v1/google/mcp` | Gemini app, Gemini CLI, Antigravity | Every endpoint uses OAuth 2.1 with PKCE. Other MCP clients, such as VS Code and Windsurf, are covered in the [MCP overview](./mcp-protocol), which also lists the smaller per-module servers. A skill is the playbook: what to check, what to ask you and in what order. The server's tools do the work in your account. Skills on their own can't reach your account, and the server on its own works but the agent has to work out the steps unaided. Tools can change between releases, so a skill names the tools it uses, and Brevo checks that they exist before each release. ## Keep skills current An agent that already has a skill uses it directly and doesn't call the server for the same text. To check, an agent connected to the server calls `list_brevo_guides` with the versions it has. To update, tell your agent "update the Brevo skills", or run the command for how you installed them: | Installed with | Update | | ------------------ | -------------------------------------------------------------------------------------------------------------------- | | Claude Code plugin | `claude plugin marketplace update brevo-skills`, then `claude plugin update brevo@brevo-skills`. Restart Claude Code | | Codex plugin | `codex plugin marketplace upgrade` | | `npx skills add` | Run `npx skills add getbrevo/brevo-skills` again | | Brevo CLI | `brevo skill update` (`brevo skill check` lists copies that are behind) | | ZIP upload | Download the new ZIP from the latest release and upload it again | ## No shell and no plugin If your agent can only connect to the Brevo MCP server, it can still load the skills from the server. Two tools are built in: * `list_brevo_guides` lists the skills. Pass the versions you already have and each one comes back as `current`, `stale`, `ahead`, `unknown` or `not_installed`, with a hint on how to update. * `get_brevo_guide` returns the full text of one skill. Your agent calls it only when the skill isn't already loaded. The `brevo-guide` skill ties these together. It tells the agent to use a skill that is already loaded, to load any other through `get_brevo_guide`, and where you can install the skills once if you want them without a tool call. The server only reads and reports. It never installs or writes anything on your machine. ### Download a skill without a shell If your agent can fetch files but not run commands, it can install a skill from the release instead: 1. Read the [catalog](https://github.com/getbrevo/brevo-skills/blob/main/catalog.json) from the [latest release](https://github.com/getbrevo/brevo-skills/releases/latest/download/catalog.json). Each skill that doesn't need a shell has a `zip_url`. 2. Download the skill's ZIP from its `zip_url`. 3. Check the file against `SHA256SUMS`, published in the same release. If you can't fetch or check the file, use `get_brevo_guide` instead. ## Use a skill Ask for the job in plain language. Your agent picks the matching skill: * "Read my Brevo brand kit and use it for my next email" * "Create a Black Friday campaign draft for my VIP list" * "Send a test of my welcome template to [me@example.com](mailto:me@example.com)" * "Create a Brevo OAuth app with the CLI" The skills create things as drafts where they can, and ask before anything you can't undo, such as sending to real contacts. ## About the skills repository [getbrevo/brevo-skills](https://github.com/getbrevo/brevo-skills) is where releases are published. Brevo writes and tests the skills in its own source repository, and each release copies them here: * `skills//`: the skills. * `.claude-plugin/`, `.cursor-plugin/`, `.grok-plugin/`, `plugin.json`, `mcp.json`, `gemini-extension.json`: the plugin files for each agent. * `catalog.json`: the list of skills, versions and SHA-256 hashes that the Brevo CLI reads. * Each release also attaches the skill ZIPs and a `SHA256SUMS` file. These files are overwritten at every release. The README, the guides in `docs/` ([platforms](https://github.com/getbrevo/brevo-skills/blob/main/docs/platforms.md) and [how skills reach agents](https://github.com/getbrevo/brevo-skills/blob/main/docs/distribution.md)) and the ChatGPT plugin build files are edited in the repository by pull request. See the [releases](https://github.com/getbrevo/brevo-skills/releases) and the [changelog](https://github.com/getbrevo/brevo-skills/blob/main/CHANGELOG.md) for what changed. ## Report a problem or contribute * To suggest a change to a skill, open an [issue](https://github.com/getbrevo/brevo-skills/issues/new/choose) on [getbrevo/brevo-skills](https://github.com/getbrevo/brevo-skills). The skills are written and tested in Brevo's own source repository, so a pull request that edits a skill can't be merged. Pull requests are welcome for the README and the docs in that repository. * Report security problems privately, as described in the repository's [security policy](https://github.com/getbrevo/brevo-skills/blob/main/SECURITY.md).