Skip to main content
Glama
org-mobicycle-ee

Cloudflare Email MCP Server

by org-mobicycle-ee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Cloudflare Email MCP Server

No user-submitted related servers found.

    Related Servers

    • imap-mcp-server

      lswith
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables querying and retrieving email messages from an IMAP mailbox via MCP tools, with an indexed storage backend on Cloudflare.
      23 npm
      MIT

    • cfmail

      askie
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to autonomously receive, search, read, reply to, and forward email through a self-hosted Cloudflare service accessible via MCP or CLI, with no web interface.
      890 npm
      MIT

    • cypht-mcp

      rjr3000
      F
      license
      Not graded
      quality
      B
      maintenance
      Cloudflare Worker implementation of the Cypht email MCP, providing eight email tools for account management, email sending, listing, viewing, searching, and deletion via IMAP.
      -

    • own-domain-mcp

      nidamen
      A
      license
      Not graded
      quality
      C
      maintenance
      Provisions own-domain email for families using Cloudflare's API, enabling automatic setup of email routing, catch-all forwarding, and verified destinations.
      MIT

    • ProtonMail MCP Server

      ronamosa
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.
      17
      9 npm
      4
      MIT

    • proton-mail-mcp

      graememeyer
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with a Proton Mail mailbox through Proton Bridge, supporting listing, searching, reading, sending, and organizing emails.
      -
    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

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clear, distinct purpose: KV operations are separated into list/count/get/put/delete/bulk_get, and email operations are separated into transfer/list/stats. There is no ambiguity between tools, even the single-key vs bulk-key get tools are clearly differentiated.

    Naming Consistency4/5

    The naming pattern is mostly consistent: KV tools use 'kv_' prefix plus resource (key/keys) plus action (list/get/put/delete), and email tools use 'email_' prefix plus action or noun. Slight inconsistencies exist like 'email_folder_stats' being noun-based rather than verb-based, and 'kv_keys_bulk_get' differs slightly in word order from 'kv_key_get'.

    Tool Count5/5

    The 9 tools cover two clear functional areas—KV key-value storage and email-to-KV transfer—without unnecessary overlap or bloat. This is within the ideal range for a purpose-built server.

    Completeness4/5

    The KV tools cover the core CRUD operations (get, put, delete, list, count) and add a useful bulk read. The email tools provide list, transfer, and stats, but lack configuration operations like approving folders or updating mappings, which are minor gaps that can be worked around via external configuration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources