Skip to main content
Glama
sapn95

epost-mcp

by sapn95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to epost-mcp

No user-submitted related servers found.

    Related Servers

    • dropscan-mcp

      bitterdev
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Dropscan postal-mail-to-email API. It enables reading and managing physical mail items, including listing, downloading scans, and (when explicitly enabled) executing actions like forwarding or destroying letters.
      21
      18 PyPI
      1
      MIT

    • outlook-web-mcp-server

      ma-nakaya
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with Outlook Web through its internal API, supporting email search, folder listing, email retrieval, read state changes, calendar events, and reply drafts without Microsoft Graph or COM.
      7
      1
      MIT

    • Grain MCP Server

      eadm
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browsing, retrieving, and downloading meeting recordings and transcripts from Grain via browser automation, bypassing the need for enterprise API access.
      2
      Apache 2.0

    • gmail-mcp

      elvisoliveira
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Gmail inbox actions (list, archive, label) as MCP tools via a browser extension and local bridge, without requiring the Gmail API or OAuth.
      2,321 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: inbox management (list, download, delete, etc.), storage operations (folders, documents), session status, and search. No two tools overlap in function; even similar operations like download_letter and read_storage_document are differentiated by context (inbox vs. storage) and output format.

    Naming Consistency5/5

    All tools follow the consistent pattern 'epost_' + verb or verb phrase in snake_case. Examples: epost_list_letters, epost_download_all, epost_move_to_folder. No mixing of conventions; the naming is predictable and readable.

    Tool Count5/5

    With 21 tools, the server covers the full scope of ePost management—inbox, storage, search, settings, and login—without being bloated. Each tool serves a necessary function, and the number is appropriate for the domain.

    Completeness5/5

    The tool surface covers the complete lifecycle for both inbox and storage: CRUD operations on letters and folders, read status management, search, archival, and trash handling. No obvious gaps; essential actions like unread count, settings, and login are included.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources