mailpal-mcp
OfficialRelated Servers
Alternatives to mailpal-mcp
No user-submitted related servers found.
Related Servers
AlicenseCqualityCmaintenanceFree email server for AI agents with hardware attestation, enabling agents to send, receive, and manage emails via MCP tools.244 npmApache 2.0- AlicenseAqualityBmaintenanceEmail for AI agents. Create inboxes, send and receive emails without phone or CAPTCHA. Inboxes are server-readable, not end-to-end encrypted.2175 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously create email accounts, verify domains, send and receive emails, and monitor delivery events without requiring human sign-up or payment.1-

AgenticMailofficial
AlicenseAqualityCmaintenanceReal email and SMS for AI agents. Run a local mail server with disposable inboxes — agents send and receive real email, fetch verification codes, and drive a real inbox without going through any third-party email API.100246MIT
Lettio MCPofficial
AlicenseAqualityBmaintenancePrivate, EU-hosted email for AI agents over the open JMAP standard. Read, search, reply in-thread, organize and send from your own mailbox; sending is pinned to the signed-in mailbox.101,778 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to work with real email: add domains with exact DNS records, create mailboxes, aliases and catch-alls, read one unified inbox across them, wait for sign-up codes and magic links, then send, reply in-thread, forward and draft. Scoped tokens with a send permission and daily cap, dry runs on every write, signed webhooks and a full audit log keep agent mail controlled.MIT
TDQS
Scored across 2 tools
The two tools are clearly distinct: one handles email, the other handles identity. There is no overlap or ambiguity between them.
Both tool names are single-word product names, lacking any verb_noun pattern. They are not descriptive of actions, and there is no consistent naming convention for operations since all actions are hidden behind a generic 'operation' parameter.
Only two tools for two domains (email and identity) is extremely thin. Each tool is a catch-all that requires further parameterization, making the count misleadingly low for the apparent scope.
The tools do not expose direct operations; they only serve as entry points to a readme. The actual functionality is not represented in the tool surface, leading to significant gaps for agents that cannot dynamically introspect.