Brevo MCP Server

account

Manage Brevo account details, senders, domains, and folders to configure marketing automation settings.

Instructions

Account management - get account info, manage senders, domains, folders

Input Schema

TableJSON Schema

Name	Required	Description
`operation`	Yes	Account operation to perform
`senderId`	No	Sender ID for sender operations
`senderData`	No	Sender information
`domain`	No	Domain name for domain operations
`folderId`	No	Folder ID for folder operations
`folderData`	No	Folder information

Implementation Reference

node_modules/@getbrevo/brevo/api/accountApi.ts:100-163 (handler)

The handler function for getting account information, matching the 'get_account' operation called in the test.

public async getAccount (options: {headers: {[name: string]: string}} = {headers: {}}) : Promise<{ response: http.IncomingMessage; body: GetAccount;  }> {
    const localVarPath = this.basePath + '/account';
    let localVarQueryParameters: any = {};
    let localVarHeaderParams: any = (<any>Object).assign({}, this._defaultHeaders);
    const produces = ['application/json'];
    // give precedence to 'application/json'
    if (produces.indexOf('application/json') >= 0) {
        localVarHeaderParams.Accept = 'application/json';
    } else {
        localVarHeaderParams.Accept = produces.join(',');
    }
    let localVarFormParams: any = {};

    (<any>Object).assign(localVarHeaderParams, options.headers);

    let localVarUseFormData = false;

    let localVarRequestOptions: localVarRequest.Options = {
        method: 'GET',
        qs: localVarQueryParameters,
        headers: localVarHeaderParams,
        uri: localVarPath,
        useQuerystring: this._useQuerystring,
        json: true,
    };

    let authenticationPromise = Promise.resolve();
    if (this.authentications.apiKey.apiKey) {
        authenticationPromise = authenticationPromise.then(() => this.authentications.apiKey.applyToRequest(localVarRequestOptions));
    }
    if (this.authentications.partnerKey.apiKey) {
        authenticationPromise = authenticationPromise.then(() => this.authentications.partnerKey.applyToRequest(localVarRequestOptions));
    }
    authenticationPromise = authenticationPromise.then(() => this.authentications.default.applyToRequest(localVarRequestOptions));

    let interceptorPromise = authenticationPromise;
    for (const interceptor of this.interceptors) {
        interceptorPromise = interceptorPromise.then(() => interceptor(localVarRequestOptions));
    }

    return interceptorPromise.then(() => {
        if (Object.keys(localVarFormParams).length) {
            if (localVarUseFormData) {
                (<any>localVarRequestOptions).formData = localVarFormParams;
            } else {
                localVarRequestOptions.form = localVarFormParams;
            }
        }
        return new Promise<{ response: http.IncomingMessage; body: GetAccount;  }>((resolve, reject) => {
            localVarRequest(localVarRequestOptions, (error, response, body) => {
                if (error) {
                    reject(error);
                } else {
                    if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
                        body = ObjectSerializer.deserialize(body, "GetAccount");
                        resolve({ response: response, body: body });
                    } else {
                        reject(new HttpError(response, body, response.statusCode));
                    }
                }
            });
        });
    });
}

node_modules/@getbrevo/brevo/model/getAccount.ts:1-40 (schema)

Input/output schema for the account information response.

/**
 * Brevo API
 * Brevo provide a RESTFul API that can be used with any languages. With this API, you will be able to :   - Manage your campaigns and get the statistics   - Manage your contacts   - Send transactional Emails and SMS   - and much more...  You can download our wrappers at https://github.com/orgs/brevo  **Possible responses**   | Code | Message |   | :-------------: | ------------- |   | 200  | OK. Successful Request  |   | 201  | OK. Successful Creation |   | 202  | OK. Request accepted |   | 204  | OK. Successful Update/Deletion  |   | 400  | Error. Bad Request  |   | 401  | Error. Authentication Needed  |   | 402  | Error. Not enough credit, plan upgrade needed  |   | 403  | Error. Permission denied  |   | 404  | Error. Object does not exist |   | 405  | Error. Method not allowed  |   | 406  | Error. Not Acceptable  |   | 422  | Error. Unprocessable Entity | 
 *
 * The version of the OpenAPI document: 3.0.0
 * Contact: contact@brevo.com
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */

import { RequestFile } from './models';
import { GetAccountAllOfMarketingAutomation } from './getAccountAllOfMarketingAutomation';
import { GetAccountAllOfPlan } from './getAccountAllOfPlan';
import { GetAccountAllOfRelay } from './getAccountAllOfRelay';
import { GetExtendedClientAllOfAddress } from './getExtendedClientAllOfAddress';

export class GetAccount {
    /**
    * Login Email
    */
    'email': string;
    /**
    * First Name
    */
    'firstName': string;
    /**
    * Last Name
    */
    'lastName': string;
    /**
    * Name of the company
    */
    'companyName': string;
    'address': GetExtendedClientAllOfAddress;
    /**
    * Information about your plans and credits
    */
    'plan': Array<GetAccountAllOfPlan>;

node_modules/@getbrevo/brevo/api/accountApi.ts:172-251 (handler)

Additional handler for account activity logs.

public async getAccountActivity (startDate?: string, endDate?: string, limit?: number, offset?: number, options: {headers: {[name: string]: string}} = {headers: {}}) : Promise<{ response: http.IncomingMessage; body: GetAccountActivity;  }> {
    const localVarPath = this.basePath + '/organization/activities';
    let localVarQueryParameters: any = {};
    let localVarHeaderParams: any = (<any>Object).assign({}, this._defaultHeaders);
    const produces = ['application/json'];
    // give precedence to 'application/json'
    if (produces.indexOf('application/json') >= 0) {
        localVarHeaderParams.Accept = 'application/json';
    } else {
        localVarHeaderParams.Accept = produces.join(',');
    }
    let localVarFormParams: any = {};

    if (startDate !== undefined) {
        localVarQueryParameters['startDate'] = ObjectSerializer.serialize(startDate, "string");
    }

    if (endDate !== undefined) {
        localVarQueryParameters['endDate'] = ObjectSerializer.serialize(endDate, "string");
    }

    if (limit !== undefined) {
        localVarQueryParameters['limit'] = ObjectSerializer.serialize(limit, "number");
    }

    if (offset !== undefined) {
        localVarQueryParameters['offset'] = ObjectSerializer.serialize(offset, "number");
    }

    (<any>Object).assign(localVarHeaderParams, options.headers);

    let localVarUseFormData = false;

    let localVarRequestOptions: localVarRequest.Options = {
        method: 'GET',
        qs: localVarQueryParameters,
        headers: localVarHeaderParams,
        uri: localVarPath,
        useQuerystring: this._useQuerystring,
        json: true,
    };

    let authenticationPromise = Promise.resolve();
    if (this.authentications.apiKey.apiKey) {
        authenticationPromise = authenticationPromise.then(() => this.authentications.apiKey.applyToRequest(localVarRequestOptions));
    }
    if (this.authentications.partnerKey.apiKey) {
        authenticationPromise = authenticationPromise.then(() => this.authentications.partnerKey.applyToRequest(localVarRequestOptions));
    }
    authenticationPromise = authenticationPromise.then(() => this.authentications.default.applyToRequest(localVarRequestOptions));

    let interceptorPromise = authenticationPromise;
    for (const interceptor of this.interceptors) {
        interceptorPromise = interceptorPromise.then(() => interceptor(localVarRequestOptions));
    }

    return interceptorPromise.then(() => {
        if (Object.keys(localVarFormParams).length) {
            if (localVarUseFormData) {
                (<any>localVarRequestOptions).formData = localVarFormParams;
            } else {
                localVarRequestOptions.form = localVarFormParams;
            }
        }
        return new Promise<{ response: http.IncomingMessage; body: GetAccountActivity;  }>((resolve, reject) => {
            localVarRequest(localVarRequestOptions, (error, response, body) => {
                if (error) {
                    reject(error);
                } else {
                    if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
                        body = ObjectSerializer.deserialize(body, "GetAccountActivity");
                        resolve({ response: response, body: body });
                    } else {
                        reject(new HttpError(response, body, response.statusCode));
                    }
                }
            });
        });
    });
}

node_modules/@getbrevo/brevo/model/getAccountActivity.ts:1-30 (schema)

Schema for account activity response.

/**
 * Brevo API
 * Brevo provide a RESTFul API that can be used with any languages. With this API, you will be able to :   - Manage your campaigns and get the statistics   - Manage your contacts   - Send transactional Emails and SMS   - and much more...  You can download our wrappers at https://github.com/orgs/brevo  **Possible responses**   | Code | Message |   | :-------------: | ------------- |   | 200  | OK. Successful Request  |   | 201  | OK. Successful Creation |   | 202  | OK. Request accepted |   | 204  | OK. Successful Update/Deletion  |   | 400  | Error. Bad Request  |   | 401  | Error. Authentication Needed  |   | 402  | Error. Not enough credit, plan upgrade needed  |   | 403  | Error. Permission denied  |   | 404  | Error. Object does not exist |   | 405  | Error. Method not allowed  |   | 406  | Error. Not Acceptable  |   | 422  | Error. Unprocessable Entity | 
 *
 * The version of the OpenAPI document: 3.0.0
 * Contact: contact@brevo.com
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */

import { RequestFile } from './models';
import { GetAccountActivityLogsInner } from './getAccountActivityLogsInner';

export class GetAccountActivity {
    /**
    * Get user activity logs
    */
    'logs'?: Array<GetAccountActivityLogsInner>;

    static discriminator: string | undefined = undefined;

    static attributeTypeMap: Array<{name: string, baseName: string, type: string}> = [
        {
            "name": "logs",
            "baseName": "logs",
            "type": "Array<GetAccountActivityLogsInner>"
        }    ];

node_modules/@getbrevo/brevo/api/apis.ts:1-66 (registration)

Exports all API classes including AccountApi, likely used for tool registration.

export * from './accountApi';
import { AccountApi } from './accountApi';
export * from './companiesApi';
import { CompaniesApi } from './companiesApi';
export * from './contactsApi';
import { ContactsApi } from './contactsApi';
export * from './conversationsApi';
import { ConversationsApi } from './conversationsApi';
export * from './couponsApi';
import { CouponsApi } from './couponsApi';
export * from './dealsApi';
import { DealsApi } from './dealsApi';
export * from './domainsApi';
import { DomainsApi } from './domainsApi';
export * from './ecommerceApi';
import { EcommerceApi } from './ecommerceApi';
export * from './emailCampaignsApi';
import { EmailCampaignsApi } from './emailCampaignsApi';
export * from './eventsApi';
import { EventsApi } from './eventsApi';
export * from './externalFeedsApi';
import { ExternalFeedsApi } from './externalFeedsApi';
export * from './filesApi';
import { FilesApi } from './filesApi';
export * from './inboundParsingApi';
import { InboundParsingApi } from './inboundParsingApi';
export * from './masterAccountApi';
import { MasterAccountApi } from './masterAccountApi';
export * from './notesApi';
import { NotesApi } from './notesApi';
export * from './paymentsApi';
import { PaymentsApi } from './paymentsApi';
export * from './processApi';
import { ProcessApi } from './processApi';
export * from './resellerApi';
import { ResellerApi } from './resellerApi';
export * from './sMSCampaignsApi';
import { SMSCampaignsApi } from './sMSCampaignsApi';
export * from './sendersApi';
import { SendersApi } from './sendersApi';
export * from './tasksApi';
import { TasksApi } from './tasksApi';
export * from './transactionalEmailsApi';
import { TransactionalEmailsApi } from './transactionalEmailsApi';
export * from './transactionalSMSApi';
import { TransactionalSMSApi } from './transactionalSMSApi';
export * from './transactionalWhatsAppApi';
import { TransactionalWhatsAppApi } from './transactionalWhatsAppApi';
export * from './userApi';
import { UserApi } from './userApi';
export * from './webhooksApi';
import { WebhooksApi } from './webhooksApi';
export * from './whatsAppCampaignsApi';
import { WhatsAppCampaignsApi } from './whatsAppCampaignsApi';
import * as http from 'http';

export class HttpError extends Error {
    constructor (public response: http.IncomingMessage, public body: any, public statusCode?: number) {
        super('HTTP request failed');
        this.name = 'HttpError';
    }
}

export { RequestFile } from '../model/models';

export const APIS = [AccountApi, CompaniesApi, ContactsApi, ConversationsApi, CouponsApi, DealsApi, DomainsApi, EcommerceApi, EmailCampaignsApi, EventsApi, ExternalFeedsApi, FilesApi, InboundParsingApi, MasterAccountApi, NotesApi, PaymentsApi, ProcessApi, ResellerApi, SMSCampaignsApi, SendersApi, TasksApi, TransactionalEmailsApi, TransactionalSMSApi, TransactionalWhatsAppApi, UserApi, WebhooksApi, WhatsAppCampaignsApi];

Tool Definition Quality

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. While it implies both read ('get') and write ('manage') operations, it doesn't specify permissions needed, rate limits, side effects, or response formats. For a tool with multiple mutation operations (create/update/delete), this is a significant gap in transparency about behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with a single sentence that efficiently communicates the tool's scope. It's front-loaded with the main purpose and follows with specific operation types. There's no wasted verbiage, though it could be slightly more structured by grouping operations more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 operations across 4 resource types), no annotations, and no output schema, the description is insufficiently complete. It doesn't explain return values, error conditions, or the relationships between operations. For a multi-function tool with mutation capabilities, more context is needed for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage, so parameters are well-documented in the structured schema. The description adds minimal value beyond the schema by listing operation categories but doesn't provide additional semantic context about parameter usage or relationships. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Account management' with specific functions listed (get account info, manage senders, domains, folders). It provides a verb+resource structure that distinguishes it from siblings like 'contacts' or 'campaigns', though it doesn't explicitly contrast with them. The purpose is specific enough to understand the scope without being tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It lists operations but doesn't indicate prerequisites, appropriate contexts, or when other tools might be more suitable. With siblings like 'contacts' and 'crm' that might overlap, this lack of differentiation leaves the agent without clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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