Mailersend MCP server

Read from the package source without running it. The installed server may list more.

• add_blocklist_recipients

  Add one or more email recipients to the blocklist suppression list for a specific domain. Blocklisted recipients will not receive emails sent through this domain.

• add_recipients_to_hard_bounces_suppression

  Add one or more email recipients to the hard bounces suppression list for a specific domain. Hard-bounced addresses will be suppressed from future email sends to prevent delivery failures.

• add_spam_complaints_recipients

  Add one or more email recipients to the spam complaints suppression list for a specific domain. Suppressed recipients will not receive emails sent through this domain.

• add_unsubscribe_recipients

  Add one or more email recipients to the unsubscribes suppression list for a specific domain, preventing them from receiving future messages.

• create_domainwrite action

  Register a new domain in the system. The domain name should be a valid fully-qualified domain name (e.g., domain.com).

• create_email_verification_listwrite action

  Create a new email verification list with a name and set of email addresses to verify. This list can be used to batch-process email validation across multiple addresses.

• create_sender_identitywrite action

  Register a new sender identity for your domain, enabling you to send emails from a specific email address with an associated display name.

• delete_blocklist_recipientswrite action

  Remove recipients from the blocklist suppression list. Use the all parameter to delete all blocklisted recipients at once, or omit it to delete specific recipients via request body.

• delete_domainwrite action

  Permanently delete a domain and remove it from the system. This action cannot be undone.

• delete_hard_bounces_recipientswrite action

  Remove recipients from the hard bounces suppression list. Set the all parameter to true to clear all hard bounced addresses, or omit it to remove specific recipients.

• delete_inbound_routewrite action

  Permanently delete an inbound route by its ID. This action cannot be undone and will remove all routing rules associated with the specified inbound route.

• delete_recipientwrite action

  Permanently delete a recipient from the system. This action cannot be undone.

• delete_scheduled_messagewrite action

  Permanently delete a scheduled message by its ID, preventing it from being sent at its scheduled time.

• delete_sender_identitywrite action

  Permanently delete a sender identity from your account. Once deleted, this identity can no longer be used to send messages.

• delete_sender_identity_by_emailwrite action

  Permanently delete a sender identity from your account using its email address. This action cannot be undone.

• delete_sms_inbound_routewrite action

  Permanently delete an SMS inbound route by its ID. This action cannot be undone and will stop processing inbound SMS messages for this route.

• delete_sms_numberwrite action

  Permanently delete an SMS phone number from your account. This action cannot be undone and will remove the number from all associated configurations.

• delete_sms_webhookwrite action

  Permanently delete an SMS webhook by its ID. Once deleted, the webhook will no longer receive SMS events.

• delete_smtp_userwrite action

  Permanently delete an SMTP user from a domain. This action cannot be undone and will immediately revoke the user's ability to send emails through this domain.

• delete_spam_complaints_recipientswrite action

  Remove recipients from the spam complaints suppression list. Use the 'all' parameter to delete all recipients at once, or omit it to delete specific recipients via request body.

• delete_tokenwrite action

  Permanently delete a token by its ID. This action cannot be undone and will immediately invalidate the token for all future requests.

• delete_unsubscribed_recipientswrite action

  Remove recipients from the unsubscribes suppression list. Set the all parameter to true to clear all unsubscribed recipients at once.

• delete_userwrite action

  Permanently delete a user account and all associated data from the system. This action cannot be undone.

• delete_webhookwrite action

  Permanently delete a webhook by its ID. This action cannot be undone and will stop all event notifications to the webhook's configured endpoint.

• get_activity

  Retrieve detailed information about a specific activity by its unique identifier.

• get_activity_data_by_date_range

  Retrieves activity data for a specified date range. Returns analytics events that occurred between the provided start and end timestamps.

• get_bulk_email_statuswrite action

  Retrieve the current status and details of a bulk email campaign. Use this to check delivery progress, completion state, and any associated metrics for a specific bulk email operation.

• get_domain

  Retrieve detailed information about a specific domain by its ID. Returns the domain's configuration, status, and metadata.

• get_domain_verification_status

  Retrieve the current verification status of a domain, including whether it has been successfully verified and any relevant verification details.

• get_email_verification_listwrite action

  Retrieve a single email verification list by its unique identifier. Use this to fetch details about a specific email verification list for review or further processing.

• get_inbound_route

  Retrieve the configuration and details of a specific inbound route by its ID. Use this to view routing rules, destination settings, and other properties of an individual inbound route.

• get_message

  Retrieve detailed information for a specific message by its ID. Returns the complete message data including content, metadata, and timestamps.

• get_opens_by_reading_environment

  Retrieves analytics data on content opens segmented by reading environment (e.g., web, mobile, app). Results are filtered by the specified date range.

• get_recipient

  Retrieve detailed information for a specific recipient by their unique identifier.

• get_scheduled_message

  Retrieve the details of a single scheduled message by its ID, including its content, schedule, and delivery status.

• get_sender_identity

  Retrieve detailed information about a specific sender identity by its ID. Use this to view configuration and settings for an individual sender identity.

• get_sender_identity_by_emailwrite action

  Retrieve a single sender identity by its email address. Use this to look up configuration and details for a specific sender.

• get_sms_inbound_route

  Retrieve the configuration and details of a specific SMS inbound route by its unique identifier.

• get_sms_message

  Retrieve a specific SMS message by its unique identifier. Returns the full message details including content, sender, recipient, timestamp, and delivery status.

• get_sms_message_activity

  Retrieve the activity history and delivery status for a specific SMS message. This includes details about message processing, delivery attempts, and any related events.

• get_sms_phone_number

  Retrieve details for a specific SMS phone number by its ID. Returns the phone number configuration and associated metadata.

• get_sms_recipient

  Retrieve detailed information about a specific SMS recipient by their unique identifier.

• get_sms_webhook

  Retrieve the configuration and details of a specific SMS webhook by its ID. Use this to inspect webhook settings, URL, event subscriptions, and other metadata.

• get_smtp_user

  Retrieve detailed information about a specific SMTP user within a domain. Use this to fetch configuration, credentials, and status for a single SMTP user account.

• get_user

  Retrieve a single user by their unique identifier. Returns the user's profile information and details.

• get_webhook

  Retrieve the details of a specific webhook by its ID. Returns the webhook configuration including its URL, events, and status.

• list_activities_for_domain

  Retrieve a list of activities for a specific domain within a given time range. Results are filtered by start and end dates in UTC.

• list_blocklist_recipients

  Retrieve all recipients currently on the blocklist suppression list. This list contains email addresses that have been suppressed from receiving communications.

• list_dns_records

  Retrieve all DNS records configured for a specific domain. Returns a collection of DNS records including their types, values, and configuration details.

• list_domains

  Retrieve a complete list of all domains available in the system. Use this operation to discover and enumerate domains for management or reference purposes.

• list_email_verification_listswrite action

  Retrieve all email verification lists available in the system. Use this to view existing verification lists and their configurations.

• list_email_verification_resultswrite action

  Retrieve the verification results for a completed email verification list. Returns detailed status and outcome information for each email address that was processed.

• list_hard_bounces_recipients

  Retrieve all recipients from the hard bounces suppression list. This list contains email addresses that have permanently failed delivery and should not receive future messages.

• list_inbound_routes

  Retrieve a list of all configured inbound routes. Use this to view routing rules for incoming messages or requests.

• list_messages

  Retrieve a list of all messages. Use this operation to fetch messages for display, filtering, or further processing.

• list_opens_by_country

  Retrieve email open metrics aggregated by country for a specified date range. Returns open counts and statistics grouped by geographic location.

• list_opens_by_user_agent

  Retrieves analytics data showing the number of opens grouped by user-agent within a specified time range. Use this to understand which browsers, devices, and applications are opening your content.

• list_recipients

  Retrieve a list of all recipients available in the system. Use this to view recipient configurations and details for message delivery or communication purposes.

• list_recipients_for_domain

  Retrieve all recipients associated with a specific domain. This returns the list of email recipients configured for the given domain.

• list_scheduled_messages

  Retrieve all scheduled messages that are queued for future delivery. Use this to view pending message schedules and their delivery status.

• list_sender_identities

  Retrieve a list of all configured sender identities available for sending messages or emails from this account.

• list_sms_activities

  Retrieve a list of all SMS activities. Use this to view the history and status of SMS messages sent through the system.

• list_sms_inbound_routes

  Retrieve all configured SMS inbound routes for your account. This returns the complete list of routes that handle incoming SMS messages.

• list_sms_messages

  Retrieve a list of all SMS messages. Use this operation to fetch SMS message records from the system.

• list_sms_phone_numbers

  Retrieve a list of all SMS phone numbers available in your account. Use this to view phone numbers configured for sending and receiving SMS messages.

• list_sms_recipients

  Retrieve a list of all SMS recipients configured in the system. Use this to view and manage contacts eligible for SMS communications.

• list_sms_webhooks

  Retrieve all SMS webhooks configured for a specific SMS phone number. This allows you to view all webhook endpoints that are currently set up to receive SMS events for the given number.

• list_smtp_users

  Retrieve all SMTP users configured for a specific domain. Returns a list of SMTP user accounts associated with the domain.

• list_spam_complaint_recipients

  Retrieve all email addresses that have been added to the spam complaints suppression list, preventing future sends to these recipients.

• list_templates

  Retrieve all available templates. Use this to discover template options for your workflows or integrations.

• list_unsubscribed_recipients

  Retrieve all recipients from the unsubscribes suppression list. This list contains email addresses that have opted out of communications and should not receive messages.

• list_users

  Retrieve a complete list of all users in the system. Returns user records with their associated metadata and details.

• list_webhooks

  Retrieve all webhooks configured for a specific domain. Returns a list of webhook configurations including their endpoints, event subscriptions, and status.

• send_bulk_emailswrite action

  Send multiple emails in a single batch request. Accepts an array of email configurations to be processed and delivered.

• send_emailwrite action

  Send an email message from a specified sender address to one or more recipients. Use this operation to deliver transactional or notification emails with a subject line and message body.

• send_smswrite action

  Send an SMS message to one or more recipients with optional personalization support. Supports template variables for dynamic content customization.

• update_domain_settingswrite action

  Update configuration settings for a specific domain. Allows modification of domain-level preferences including content tracking behavior.

• update_inbound_routewrite action

  Update configuration settings for an inbound route, including its name, domain enablement, priority, and filtering rules. Changes take effect immediately for new incoming requests matching this route.

• update_sender_identitywrite action

  Update the configuration of an existing sender identity, such as its display name. This allows you to modify how your sender identity appears in outgoing communications.

• update_sender_identity_by_emailwrite action

  Update the configuration of a sender identity using its email address. Allows modification of sender identity properties such as the display name.

• update_sms_inbound_routewrite action

  Update an existing inbound SMS route configuration, including the associated phone number, display name, webhook destination, and activation status.

• update_sms_phone_number_pause_statuswrite action

  Update the pause status of an SMS phone number. Use this to temporarily disable or re-enable an SMS phone number for sending messages.

• update_sms_recipient_statuswrite action

  Update the subscription status of an SMS recipient. Use this to activate a recipient or mark them as opted out from SMS communications.

• update_sms_webhookwrite action

  Update the configuration of an SMS webhook by enabling or disabling it. This allows you to control whether the webhook is active without deleting it.

• update_smtp_userwrite action

  Update an SMTP user's configuration within a domain, including their display name and enabled status.

• update_token_statuswrite action

  Update the operational status of a token by pausing or activating it. Use this to control whether a token is currently active or temporarily paused.

• update_user_rolewrite action

  Update the role assignment for a specific user. This operation allows you to change a user's access level or permissions by assigning them a new role (e.g., Admin).

• verify_emailwrite action

  Verify the validity and deliverability of an email address. This operation checks whether the provided email address is properly formatted and active.

• verify_email_verification_listwrite action

  Verify an email verification list by its ID. This operation processes and validates the email addresses in the specified verification list.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

89

the typical server has 7

Tools that change things

46%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

150

more than 71% of 12,191 servers with a package

Mailersend: common questions

Is Mailersend MCP server safe?

Mostly: it is graded B (80/100). Read the Mailersend safety report

How do I install Mailersend?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Mailersend need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Mailersend maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.2.

How does Mailersend compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 89 (the typical server has 7); tools that change things 46% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.