brevo
Brevo ships a hosted, remote MCP server at https://mcp.brevo.com. An agent POSTs directly to the endpoint with a Bearer MCP token minted in the Brevo dashboard (Account > SMTP & API > API Keys, with the "Create MCP server API key" toggle on) — no local install required. Brevo splits the surface into one combined server covering 27 modules and 27 per-module servers, so a client can load a narrower tool set. The endpoint also advertises RFC 8414 authorization-server metadata with dynamic client registration and PKCE, so an OAuth client can register itself rather than pasting a static token.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.