Skip to main content
Glama
samuelar2

sentvia-mcp

by samuelar2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to sentvia-mcp

No user-submitted related servers found.

    Related Servers

    • OutreachEmailMCP

      BreazyLabs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as an email gateway for Gmail and Microsoft 365, enabling AI agents to send and read emails via MCP tools, with SMTP/IMAP and REST APIs for email sequencing and automation.
      1
      AGPL 3.0

    • agentbox

      sagnik11
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that gives AI agents programmable email inboxes with tools to create inboxes, send and list threaded email, and search messages.
      3 npm
      1
      MIT

    • PostStack MCP Server

      getpoststack
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for the PostStack email API that enables AI assistants to send transactional emails, manage contacts, handle inbound email threads, and perform deliverability checks through 84 curated tools.
      84
      24 npm
      1
      MIT

    • mail-mcp

      KpihX
      A
      license
      Not graded
      quality
      D
      maintenance
      A generic IMAP and SMTP MCP server that enables AI agents to interact with email accounts for reading, searching, and sending messages. It provides high-level tools for managing email workflows like daily digests and folder organization across any standard email provider.
      1
      MIT

    • Email MCP Server

      chinmay4382
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI models to read, search, and send emails via IMAP and SMTP protocols. It supports various providers like Gmail and Outlook, allowing for tasks such as retrieving unread messages, searching by sender, and managing mailbox folders.
      -
    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.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: webhooks, inboxes, address rules, domains, messages, threads, and drafts are all clearly separated. The send/reply/forward trio is differentiated by their descriptions, so there is no ambiguity in tool selection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_inbox, list_drafts, delete_webhook). The occasional use of 'add' instead of 'create' (add_domain, add_address_rule) is a minor synonym variation, not a structural inconsistency.

    Tool Count4/5

    With 21 tools, the server is slightly larger than the typical 3-15 range, but this is justified by the breadth of the email platform (inboxes, domains, messages, threads, drafts, webhooks, and rules). Every tool has a clear purpose, so the count feels appropriate rather than bloated.

    Completeness4/5

    The tool surface covers core CRUD for inboxes and webhooks, plus sending, searching, threads, and drafts. Minor gaps exist, such as no delete for drafts or domains, but these can be worked around (e.g., by recreating resources). No major lifecycle dead ends are present.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources