naver-mail-mcp
Related Servers
Alternatives to naver-mail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables local AI apps such as Codex and Claude Desktop to search, read, send, and manage NAVER Mail through IMAP/SMTP, including HTML emails and attachments.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, schedule, manage, and analyze mail across multiple IMAP/SMTP accounts, with provider-aware labels, real-time IDLE watching, verification-code capture, and OAuth2 support. Connects over stdio or Streamable HTTP, exposing 52 tools, 7 prompts, and 6 resources with a guided setup wizard.11 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, and analyze email across multiple IMAP/SMTP accounts, with drafts and templates, provider-aware labels and bulk operations, calendar extraction, real-time inbox watching with AI triage, and verification-code capture. Exposes 52 tools, 7 prompts, and 6 resources over stdio or Streamable HTTP, with OAuth2 support for Gmail and Microsoft 365.11 npmISC
- AlicenseNot gradedqualityCmaintenanceStreamable HTTP MCP server for Gmail that enables AI agents to search threads, read messages, manage drafts, and organize the inbox via OAuth authentication.530 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and read email, inspect attachments, and optionally send messages and organize folders through existing IMAP and SMTP mailboxes. Supports Docker, stdio, and HTTPS OAuth deployment with read-only or full-access modes.MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents a self-hosted Cloudflare mailbox they can use to receive, search, wait for, read, send, reply to and forward email, with attachments and threads, over MCP or REST behind a single bearer token.5MIT
TDQS
Scored across 30 tools
Most tools target a clear resource+action pair (message vs thread vs label vs draft), but there is real redundancy: update_message_labels duplicates what label_message + unlabel_message already do, and reply overlaps heavily with send_message when replyToMessageId is supplied. The message-vs-thread variants (trash_message/trash_thread, mark_message_spam/mark_thread_spam) are distinguishable only via the name suffix, which descriptions support but don't strongly disambiguate.
Strong verb_noun snake_case pattern with predictable prefixes (label_/unlabel_, trash_/untrash_, mark_/unmark_, create_/update_/delete_). A few bare-verb outliers (reply, forward, send_message) break the pattern slightly, but overall it is highly predictable.
30 tools is heavy and crosses the comfortable range, though a full mail client (messages, threads, drafts, labels, spam/trash, sending) is a genuinely broad domain. Removing the redundant update_message_labels and collapsing mark/unmark pairs would bring it to a well-scoped size.
Covers the full lifecycle for messages, threads, drafts (create/get/update/delete), labels (CRUD), plus send/reply/forward and attachment download. Minor gaps: no way to attach files when sending and no permanent-delete operation, but these are likely deliberate and workaroundable.