Skip to main content
Glama
beylessai

Hiworks Mail MCP

by beylessai

Related Servers

Alternatives to Hiworks Mail MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for email operations supporting IMAP and SMTP protocols, enabling sending, receiving, searching, and managing emails with attachments.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Naver Mail that enables reading, searching, downloading and organizing attachments, and preparing draft emails without sending automatically.
      -
    • F
      license
      B
      quality
      Not graded
      maintenance
      This MCP server enables users to manage emails via POP3 and SMTP protocols, allowing for listing, searching, reading, and sending messages. It also supports fetching email threads and extracting text content from various document attachments including PDFs and Office files.
      8
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables applications to interact with Gmail through a clean API, supporting email searching, sending, reading, and label management.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enables email operations through POP3 and SMTP protocols in Cursor AI, allowing users to send, receive, list, and manage emails using natural language commands.
      301 npm
      48
      MIT

    TDQS

    C2.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: read_email retrieves emails, read_username fetches usernames, search_email finds emails based on criteria, and send_email sends emails. The descriptions are straightforward and unambiguous, making tool selection easy for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., read_email, send_email). This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count4/5

    With 4 tools, the count is reasonable for an email management server, covering core operations like reading, searching, and sending emails, plus username retrieval. It is slightly lean but well-scoped for basic functionality, though additional tools like deleting or managing folders might enhance completeness.

    Completeness3/5

    The tools cover essential email operations (read, search, send) and username access, but there are notable gaps in lifecycle management, such as deleting emails, managing folders, or handling attachments. While agents can perform basic tasks, the lack of update or delete functions limits full email workflow coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues