Mailersend

Created By
MailerSend7 months ago
The MailerSend MCP server lets you connect AI tools directly to your MailerSend account for real-time email management using the most current data. Use natural language prompts to send emails, manage domains, analyze performance, troubleshoot, and more. Quick and easy setup, just connect, authorize and start handling transactional email tasks faster and smarter.
Overview

What is MailerSend MCP Server?

MailerSend MCP Server is a beta version of the Model Context Protocol (MCP) server that facilitates seamless integration with MailerSend's email marketing API, allowing AI assistants to manage subscribers, campaigns, and groups through standardized tools.

How to use MailerSend MCP Server?

To use the MailerSend MCP Server, connect any MCP-compatible client to the server using the endpoint https://mcp.mailersend.com/mcp. You can configure various clients like Claude, Gemini CLI, or VSCode to interact with the server.

Key features of MailerSend MCP Server?

  • Standardized protocol for AI assistants to interact with email marketing systems.
  • Support for managing email campaigns, subscribers, and analytics.
  • Integration capabilities with various tools and platforms.

Use cases of MailerSend MCP Server?

  1. Automating email marketing campaigns through AI.
  2. Managing subscriber lists and email templates efficiently.
  3. Analyzing email performance and engagement metrics.

FAQ from MailerSend MCP Server?

  • What is the MCP?

The Model Context Protocol (MCP) is a standardized protocol for AI assistants to interact with external systems, enabling seamless communication and task execution.

  • Is the MailerSend MCP Server free to use?

Yes, the MailerSend MCP Server is available for free during its beta phase.

  • How can I provide feedback?

You can send your feedback to mcp@mailersend.com.

Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
MailerSend
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago