Skip to main content
Glama
shipmail-to

shipmail-mcp

by shipmail-to
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to shipmail-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      94 npm
      2
      MIT

    • Fastmail MCP Server

      i11v
      A
      license
      Not graded
      quality
      D
      maintenance
      An unofficial MCP server that enables users to manage their Fastmail accounts through natural language interactions. It provides tools to query mailboxes, retrieve email content with advanced filtering, and send messages directly through the Fastmail API.
      76 npm
      MIT

    • 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
    • @curviate/mcp by Curviate

      @curviate/mcpofficial

      Curviate
      A
      license
      Not graded
      quality
      C
      maintenance
      Official MCP server for the Curviate API, enabling AI agents to perform LinkedIn actions like profile management, messaging, posting, and advanced search, with Sales Navigator and Recruiter support.
      4 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

    B3.2/5.0

    Scored across 136 tools

    Disambiguation2/5

    Most tools are cleanly separated by resource, but the message/thread/reply cluster is dangerously overlapping: four reply tools (reply_to_message, reply_to_inbox_message, reply_to_thread, reply_to_inbox_thread) and multiple message/thread listers differ only by ID prefix or mailbox scope. At 136 tools, these subtle distinctions invite frequent misselection.

    Naming Consistency5/5

    All 136 tools follow the shipmail_verb_noun snake_case pattern with remarkable discipline: get_/list_/create_/update_/delete_/send_/cancel_/resume_ prefixes are used consistently, and compound verbs like rotate_webhook_secret and prepare_staged_attachment_upload are still recognizable. There is no mixing of case styles or vague generic verbs.

    Tool Count1/5

    136 tools is an extreme count, roughly ten times the upper bound of a well-scoped MCP server. Even though the tools span distinct product areas, the sheer volume forces agents to navigate an unwieldy surface and dramatically increases the chance of selecting the wrong tool for a task.

    Completeness4/5

    Within each declared domain the lifecycle coverage is thorough: full CRUD exists for mailboxes, folders, webhooks, audiences, subscribers, calendar events, and booking pages, plus operational extras like export/import, preflight, replay, and scan tools. Minor gaps exist such as no sent-message delivery status tracking and no DNS record editing, but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources