integration-brevo

Connect a self-hosted Hermes agent to Brevo's MCP server over SSH.

13|1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/paarths-collab/hstack --skill integration-brevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-brevo
Source: https://github.com/paarths-collab/hstack/tree/main/skills/integration-brevo
Command: npx skills add https://github.com/paarths-collab/hstack --skill integration-brevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of connecting Brevo to a self-hosted Hermes agent so AI assistants can send campaigns, manage contacts, and read marketing analytics over SSH.

Core Features & Use Cases

  • Brevo MCP Connection: Registers Brevo’s first-party remote MCP server on a Hermes VPS using an MCP-enabled token.
  • Marketing Workflow Automation: Supports email, SMS, CRM actions, contact management, and automation tasks through AI coding agents.
  • Safe Operational Flow: Uses idempotent checks, dry-run previews, verification steps, and rollback logic to reduce deployment risk.

Quick Start

Ask the AI to connect Brevo to your Hermes server using your MCP-enabled Brevo token and a verified sender so it can register the service, reload the gateway, and confirm the integration.

Frequently Asked Questions about integration-brevo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Brevo to a self-hosted Hermes agent for marketing automation?

Connecting Brevo to a Hermes agent involves registering the Brevo remote MCP server on your VPS using an MCP-enabled token and a verified sender to enable campaign management over HTTPS.

Can I use Brevo MCP with AI coding agents like Claude Code or Cursor?

Yes, the Brevo MCP integration supports Claude Code, Codex, Cursor, and Gemini CLI by wiring the remote MCP connection over HTTPS to enable CRM actions and email workflows.

What do I need to set up Brevo marketing workflows over SSH?

Setting up Brevo workflows over SSH requires an MCP-enabled Brevo token, a validated sender or domain, and an SSH-first deployment, using idempotent checks and rollback logic for safe gateway registration.

How does rollback logic work when registering a remote MCP server?

Rollback logic ensures safe MCP server registration by applying idempotent checks, dry-run previews, and verification steps to reduce deployment risk during remote gateway reloads.

Are there limitations when using Brevo for contact management through AI agents?

The main constraint is requiring an SSH-first deployment and an MCP-enabled Brevo token. Without a validated sender or domain, the AI agent cannot safely execute contact management tasks.