Skip to main content
Glama
gentlerai001

NAVER Mail MCP

by gentlerai001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to NAVER Mail MCP

No user-submitted related servers found.

    Related Servers

    • naver-works-mail-mcp

      jaykim81
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables reading and sending Naver Works emails (Korean business email service) through Claude Desktop using IMAP/SMTP with app passwords.
      -

    • Naver Mail MCP Server

      Leonamin
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables users to interact with their Naver Mail account via the Model Context Protocol. It allows for seamless mail integration and management within MCP-compatible clients like Claude Desktop.
      16
      -

    • K-Mail-MCP

      youngsooco
      F
      license
      B
      quality
      D
      maintenance
      K-Mail-MCP is an MCP server that connects 6 mail services — Naver, Daum/Kakao, Gmail, Nate, Yahoo, and iCloud — to Claude AI. It enables AI-powered email summarization, translation, spam detection, and unified inbox management — all with AES-256-GCM encrypted credentials.
      8
      6
      -

    • IMAP MCP

      abconsultdev
      A
      license
      A
      quality
      A
      maintenance
      Lets Claude Desktop read any IMAP mailbox and send emails via SMTP, with support for multiple mailboxes and locally stored credentials.
      13
      33 npm
      MIT

    • mcp-mail-server

      robotic-wings
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and manage email via IMAP, and send emails with attachments via SMTP, using natural language commands.
      1,438 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool maps to a distinct action (setup, verify, list mailboxes, search, read, list/download attachments, send). Minor overlap exists between get_email (which also returns attachment metadata) and list_attachments, but the descriptions clearly differentiate their purposes.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (list_mailboxes, search_emails, get_email, download_attachment, send_email). No mixed conventions or vague standalone verbs.

    Tool Count5/5

    Eight tools is well-scoped for a mail server covering auth/setup, discovery, search, read, attachments, and send. Each tool earns its place without redundancy.

    Completeness3/5

    Core read/send/search/attachment workflows are covered, but there are no update or lifecycle operations such as mark read/unread, flag, delete, or move messages. These notable gaps limit agents to read-only plus send scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources