Skip to content

Add MailySend MCP server to Communication & Messaging - #2326

Open
GagnDeep wants to merge 1 commit into
TensorBlock:mainfrom
GagnDeep:add-mailysend
Open

Add MailySend MCP server to Communication & Messaging#2326
GagnDeep wants to merge 1 commit into
TensorBlock:mainfrom
GagnDeep:add-mailysend

Conversation

@GagnDeep

Copy link
Copy Markdown

Adds GagnDeep/mailysend to Communication & Messaging.

MailySend is an MIT-licensed email platform you deploy into your own Cloudflare account (Workers, D1, R2, KV, Queues, Durable Objects, Email Routing) or run on a plain Node 24 server. The MCP endpoint is part of the same deployment.

  • Transport: Streamable HTTP at /mcp on your own instance.
  • Auth: bearer API key, scoped and stored hashed; restricted keys are rejected.
  • Tools (9): send_email, reply_to_thread, list_emails, get_email, search_threads, get_thread, list_domains, get_analytics, create_contact.
  • Human in the loop: sends and replies become pending confirmations approved at /app/approvals; the agent cannot approve its own send.
  • License: MIT. Docs: https://mailysend.com/docs

What distinguishes it from the other email entries in this category: it is not a wrapper over someone else's mailbox or a hosted inbox API. The infrastructure is yours — your sending domains, your DKIM, your stored messages and analytics — so nothing about the agent's mail leaves the account you control.

Disclosure: I am the author and maintainer.

🤖 Generated with Claude Code

https://claude.ai/code/session_017W45rMUr33JaPsozekrCn6

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017W45rMUr33JaPsozekrCn6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant