Skip to main content
Glama
DanielRohregger

stratomcp

by DanielRohregger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to stratomcp

No user-submitted related servers found.

    Related Servers

    • email-mcp

      skyttedk
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read, search, draft, send, flag, and move email across multiple IMAP/SMTP mailboxes while keeping credentials local.
      -

    • strato-mail-mcp

      Ragazzoforte
      F
      license
      B
      quality
      D
      maintenance
      Enables Claude to read, send, and manage emails via IMAP/SMTP for Strato mail accounts, including folder navigation, attachment handling, and draft management.
      15
      -

    • IMAP MCP

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

    • IMAP MCP

      WEYERSK
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to read, manage, and send email from any IMAP mailbox over plain IMAP and SMTP, including hosting-company and self-hosted mail servers. It provides tools for searching, reading, moving, deleting, and composing messages while built-in safety rules prevent unintended changes.
      12
      MIT

    • mail-macos-mcp

      Maxtechexplore
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to control the macOS Mail app for reading, searching, drafting, sending, and managing emails directly from Claude Desktop.
      12
      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

    A3.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (list, read, send, flag, move, draft, attachments). The only real overlap is search_messages vs search_index, but the descriptions explicitly differentiate them (per-folder IMAP envelope search vs ranked local full-text index) and even state a preference, so misselection is unlikely.

    Naming Consistency4/5

    Almost all tools follow a clean verb_noun snake_case pattern (list_folders, get_message, send_message, move_messages, sync_index). The lone deviation is index_stats, which is noun-only, but it's still readable and predictable within the index_* family.

    Tool Count5/5

    12 tools is well-scoped for a mail server, with each tool covering a distinct capability (accounts, folders, search, read, send, drafts, flags, move, attachments, index maintenance). Nothing feels redundant or filler.

    Completeness4/5

    Core read/write lifecycle is covered: search, read, send, draft, flag, move, attachments, and index management. Minor gaps exist (no explicit folder create/delete, no reply/forward, no permanent delete beyond move-to-trash), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources