Skip to main content
Glama
Sign In
Wraps Email for Amazon SES

Wraps Email for Amazon SES

by wraps-team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Wraps Email for Amazon SES

No user-submitted related servers found.

    Related Servers

    • email-mcp

      yashjoshiatgit
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that empowers AI agents to securely send emails via SMTP, supporting plain text, HTML, and attachments.
      MIT

    • MepMail

      JE4NVRG
      A
      license
      A
      quality
      A
      maintenance
      Local stdio MCP package for transactional email, sending domains and Correio mailboxes for AI agents, subject to team and mailbox permissions. @mepmail/mcp (MIT, Node >=20) implements a documented subset of the separately hosted OAuth service.
      28
      AGPL 3.0

    • mcp-email-sender

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to validate email addresses and send emails via SMTP with zero external dependencies.
      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
    • fagents-mcp

      fagents-mcpofficial

      fagents
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables Claude Code agents to send and read emails via SMTP/IMAP with per-agent credential isolation and audit logging.
      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

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern—account setup status, sending, cost estimation, delivery events, send history, suppressions, and domain verification—with clear boundaries. The closest pair, get_setup_status and verify_domain_status, operate at different levels (account vs. domain) and their descriptions make that explicit.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: get_, send_, estimate_, list_, and verify_. The verbs are appropriate to each action, and there is no mixing of styles or vague generic terms.

    Tool Count5/5

    Seven tools is well-scoped for an email-sending service. Each tool covers a necessary capability—setup, sending, cost, logging, history, suppression checking, and domain verification—without redundancy or bloat.

    Completeness4/5

    The tool surface covers the core email workflow: understand sandbox status, verify domains, send, check recent sends, inspect event logs, and avoid suppressed addresses. Minor gaps exist such as no tool to manage suppressions or perform domain verification actions, but agents can work around these using the existing status and listing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources