Mektup-mcp
Related Servers
Alternatives to Mektup-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register domains, manage DNS, create mailboxes, and send/receive email through typed tools.197 npm2MIT
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to read, search, compose, and send emails by connecting to any IMAP/SMTP provider. It supports comprehensive mailbox management, including draft handling and message deletion, directly through natural language.10286 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, search, send, and manage emails via IMAP/SMTP with OAuth 2.1 authentication, supporting folders, drafts, replies, and forwarding.MIT
- FlicenseBqualityDmaintenanceEnables AI models to send, receive, search, and manage emails via SMTP/IMAP, including support for attachments, contacts, and advanced search.18-
- AlicenseBqualityDmaintenanceEnables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.1613 npm1MIT
TDQS
Scored across 45 tools
Every tool targets a distinct resource and action—account, domains, mailboxes, forwards, identity, vacation, folders, contacts, drafts, and messages are clearly separated. The only potential confusion is between list_messages/get_thread/get_message, but the descriptions explain the hierarchy. No two tools appear to do the same thing.
Tools overwhelmingly follow a verb_noun snake_case pattern (list_*, get_*, create_*, update_*, delete_*). Minor deviations like add_forward/remove_forward, reset_mailbox_password, verify_domain, send_email, and download_attachment are still verb-first and readable, but they break the strict CRUD verb consistency.
At 45 tools, the server far exceeds the typical well-scoped range and crosses the 'too many' threshold. Each tool is individually justifiable given the breadth of subdomains (account, domains, mailboxes, webhooks, contacts, drafts, messages), but the overall surface is heavy for agents to navigate.
The tool set provides CRUD/lifecycle coverage for almost every resource: domains, mailboxes, webhooks, contacts, drafts, and messages. Minor gaps exist—no explicit send-draft action, no attachment handling in send_email, no folder rename or single-mailbox get—but agents can work around them.