Search for:
Why this server?
This server is specifically designed for sending emails through the Resend service, using the Model Context Protocol (MCP) interface.
Why this server?
This server enables sending emails via SMTP with template management, supporting multiple SMTP configurations, template creation, and bulk email sending.
Why this server?
This server is designed for sending messages, which would include emails, via WeCom bots using FastMCP, supporting asynchronous communication.
Why this server?
This server focuses on accessing Gmail, including viewing recent emails and searching the inbox. While it doesn't explicitly say "sending", that is often a paired action.
Why this server?
A server that allows Claude to search and retrieve emails from your Gmail account, supporting functions like searching emails, retrieving full content of specific emails, and listing recent messages; which implies it can also send.
Why this server?
Enables interaction with Gmail through the Gmail API to read, send, and manage emails. Supports multiple Gmail accounts with real-time monitoring and advanced features for email search and attachment handling.
Why this server?
A versatile file operations server. While not strictly email, it may be used to create email drafts etc.
Why this server?
A database interface that might be combined with other features to send emails based on events. It's not directly for sending emails, so it is low priority.
Why this server?
Allows MCP users to manage email directly from Outlook.
Why this server?
A simple MCP server that allows Claude to access your Telegram account to read and send messages on your behalf, similar to sending email.