Skip to main content
Glama

Brevo MCP Server

smithery.yaml•1.44 kB
version: 1 startCommand: type: stdio configSchema: type: object required: ['apiKey'] properties: apiKey: type: string description: "Brevo API key for authentication (get from https://app.brevo.com/settings/keys/api - required)" defaultSenderEmail: type: string description: "Default sender email address (must be verified in Brevo, e.g., your-email@yourdomain.com)" defaultSenderName: type: string description: "Default sender name for emails (e.g., 'Your Company Name' or 'John Doe')" debug: type: boolean description: "Enable debug mode for additional logging (true/false)" default: false commandFunction: |- (config) => ({ command: 'node', args: ['build/index.js'], env: { BREVO_API_KEY: config.apiKey, BREVO_DEFAULT_SENDER_EMAIL: config.defaultSenderEmail || '', BREVO_DEFAULT_SENDER_NAME: config.defaultSenderName || '', DEBUG: config.debug ? 'true' : 'false' } }) exampleConfig: apiKey: "xkeysib-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxxxxxxx" defaultSenderEmail: "noreply@yourdomain.com" defaultSenderName: "Your App Name" debug: false description: "šŸ“§ Brevo MCP Server - Send transactional emails, SMS, and manage contacts through Brevo API" tags: - "email" - "sms" - "marketing" - "transactional" - "brevo"

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samihalawa/brevo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server