Skip to main content
Glama
Sendmux

Sendmux Email Inbox API + Sending

Official
by Sendmux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Sendmux Email Inbox API + Sending

No user-submitted related servers found.

    Related Servers

    • sendook-mcp

      StreamlinedStartup
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.
      16
      MIT

    • mailbox-mcp

      arbengine
      A
      license
      A
      quality
      C
      maintenance
      Official mailbox.bot MCP server for AI agents. Send letters, certified mail, postcards, and receive scanned inbound physical mail with sandbox keys, approval controls, tracking, and webhooks.
      29
      40 npm
      2
      MIT

    • send16-mcp

      spruikco
      A
      license
      B
      quality
      A
      maintenance
      The email API your AI agent can actually use. A Model Context Protocol server for Send16 that gives Claude, Cursor, and any MCP client 79 tools to send transactional & marketing email, manage contacts, audiences, segments, automations, templates, the inbox, suppressions, and webhooks.
      79
      24 npm
      MIT

    • sentvia-mcp

      samuelar2
      A
      license
      A
      quality
      D
      maintenance
      MCP server for SentVia that provides email infrastructure for AI agents, enabling them to create inboxes, send, reply, forward, search messages, manage drafts, domains, webhooks, and allow/block rules through 21 tools.
      21
      48 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

    A3.8/5.0

    Scored across 32 tools

    Disambiguation3/5

    The mailbox_ and sending_ prefixes help separate the two domains, but several tools have overlapping purposes: mailbox_get_message, mailbox_list_body, and mailbox_list_content all read message content, while mailbox_list_messages and mailbox_search_message_snippets both filter messages by similar criteria. The descriptions help, but an agent could easily pick the wrong tool without careful reading.

    Naming Consistency4/5

    Naming mostly follows a consistent mailbox_/sending_ prefix plus verb_noun pattern, and batch operations are clearly marked with batch_. Minor inconsistencies exist, such as mailbox_read_attachment vs mailbox_get_attachment and sending_send_email being somewhat redundant, but overall the pattern is predictable and readable.

    Tool Count2/5

    32 tools is above the 25-tool threshold for 'too many' and feels heavy even for a combined inbox and sending API. The count is inflated by multiple closely related read tools (get_message, list_body, list_content) and several connection/profile/session inspection tools that could likely be consolidated.

    Completeness5/5

    The surface appears comprehensive for an email inbox and sending API: messages can be listed, searched, counted, read, batch-updated, batch-deleted, and sent; attachments support upload, read, and presigned download; threads and folders are covered; and connection validation plus identity management is included. No major dead ends are obvious.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources