ForwardEmail MCP Server
Related Servers
Alternatives to ForwardEmail MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables secure mailbox access and email management via IMAP/SMTP, with tools for reading, searching, organizing, sending, and deleting emails, designed for local use and compatible with MCP clients like ChatGPT.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with access to PurelyMail's email management API, enabling user, domain, routing, and billing management through natural language.82 npm10MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Fastmail services, providing tools for comprehensive email management, contact searching, and calendar event coordination via the JMAP API. It supports advanced features like threaded conversations, attachment handling, and bulk mailbox operations through natural language.28MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, manage, schedule, and analyze emails across multiple IMAP/SMTP accounts via MCP, with features like OAuth2, calendar extraction, analytics, and real-time email watching.502 npmLGPL 3.0
- AlicenseAqualityCmaintenanceAn MCP server that provides AI assistants with full access to Fastmail accounts for managing email, contacts, calendars, and file storage. It implements 42 tools across JMAP, CardDAV, CalDAV, and WebDAV protocols to enable comprehensive account interaction through natural language.48MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read, search, send, and manage email across multiple IMAP/SMTP accounts through OAuth 2.1-secured MCP tools.MIT
TDQS
Scored across 71 tools
Several tools have overlapping purposes, most notably the domain_sieve_* and sieve_script_* groups, which both manage Sieve scripts for an alias with nearly identical descriptions. Other resources like email vs message also blur the line between outbound SMTP and IMAP messages, though descriptions help somewhat.
Naming is inconsistent: list endpoints use plural resource names (domains_list, aliases_list, contacts_list), while other actions use singular (domain_create, alias_get, contact_update). Prefixes vary as well, with domain_sieve_* and sieve_script_* both used for the same underlying resource.
With 71 tools, the server is far beyond the typical 3-15 well-scoped range and even exceeds the 25+ threshold that indicates too many. While the API covers a broad feature set, the sheer number makes it unwieldy for an agent to navigate efficiently.
The tool surface is remarkably comprehensive, covering CRUD for accounts, domains, aliases, contacts, calendars, events, messages, folders, and Sieve scripts, plus email sending and domain verification. Minor gaps exist, such as no getter for allowlist/denylist (only replace) and duplication between Sieve tool groups, but most workflows have no dead ends.