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
      D
      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
      70 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
      77 npm
      MIT

    • SentFromAI Email MCP for

      sentfromai
      A
      license
      A
      quality
      A
      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
      237 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 plus mostly distinct resource/action pairs make the surface navigable, but several tools are easy to confuse: get_message/list_body/list_content, get_attachment/read_attachment, and the two upload-attachment variants have overlapping boundaries. An agent would need to read descriptions carefully to avoid selecting the wrong one for a content-heavy task.

    Naming Consistency5/5

    All tools follow a consistent snake_case prefix_verb_noun pattern, with mailbox_ and sending_ clearly separating the two API domains. Names like sending_create_attachment_upload are verbose but still predictable and consistent with the rest of the set.

    Tool Count2/5

    With 32 tools, this exceeds the comfortable range and pushes into the too-heavy zone. Many tools could be consolidated, especially the multiple body/content/attachment retrieval variants, even though the split between mailbox and sending operations is logical.

    Completeness4/5

    The set provides strong end-to-end coverage for email: message retrieval, search, threads, folders, attachments, mutation, and both single and batch sending. Minor gaps such as no folder creation/deletion or attachment cleanup prevent a perfect score, but agents should not hit dead ends in normal email workflows.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources