Email Sending MCP
Related Servers
Alternatives to Email Sending MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows Claude Desktop or Cursor to send emails directly using Resend's API, eliminating the need to copy-paste email content.ISC
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides email sending functionality using Protonmail's SMTP service. It allows both Claude Desktop and Cline VSCode extension to send emails on your behalf using your Protonmail credentials.51MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server for interacting with Resend's email API, auto-generated using AG2's MCP builder to enable sending emails through natural language.-
- AlicenseAqualityFmaintenanceAn MCP server for the Resend email API, enabling AI assistants to send emails, manage contacts, audiences, and domains through natural language.1838 npmMIT

Pidgely MCPofficial
AlicenseBqualityBmaintenanceMCP server for Pidgely, an email API: lets Claude, Cursor and other AI agents send email and manage domains, contacts and broadcasts.74MIT- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that enables Claude Desktop to manage emails via SMTP and IMAP. Send emails, fetch unread messages, and create draft replies directly from conversations.318 npmMIT
TDQS
Scored across 137 tools
Descriptions are unusually disciplined: nearly every tool carries explicit "NOT for" guidance steering agents to the right sibling (e.g. send-email vs send-broadcast vs send-new-inbox-email vs send-inbox-draft vs reply/forward-inbox-thread-email). A few pairs remain genuinely close — get-inbox-thread vs list-inbox-thread-emails, get-automation's list mode vs its get mode, and manage-events (a multi-action tool) sitting alongside the single-action tools — but these are edge cases rather than systemic overlap.
The dominant pattern is kebab-case verb_noun (list-contacts, create-broadcast, remove-domain, get-webhook-event), applied consistently across most resource families. Deviations are minor: prepositional forms like connect-to-editor/disconnect-from-editor, the vague catch-all manage-events, and verbless noun-ish helpers, but nothing is camelCase or chaotic.
137 tools is far beyond what an agent can select from reliably, even though the Resend surface is genuinely broad (emails, broadcasts, contacts, segments, topics, domains, webhooks, inboxes/threads/labels/drafts, automations, events, templates, suppressions, keys, logs). Many families are split into fine-grained variants (add/set/remove thread labels, add/batch-add/remove/batch-remove suppressions) that inflate the count past usefulness. Scoping or consolidating would materially improve usability.
Coverage is impressive: full CRUD for contacts, segments, topics, domains, webhooks, templates, broadcasts, inboxes, threads, labels, drafts, automations, events, suppressions, API keys, and contact properties, plus imports, logs, metrics, and OAuth grants. The notable gaps are deliberate or minor — attachment contents cannot be downloaded (only listed), and there is no equivalent of a reply/forward for plain transactional email — but no core workflow dead-ends.