Skip to main content
Glama
Choppaaahh

sendgrid-mcp-secure

by Choppaaahh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sendgrid-mcp-secure

No user-submitted related servers found.

    Related Servers

    • smtp-mcp

      ni-c
      A
      license
      A
      quality
      A
      maintenance
      MCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation
      4
      46 npm
      MIT

    • mcp-mail

      PilarJ
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing read and send access to a single IMAP/SMTP mailbox over Streamable HTTP with GitHub OAuth authentication, featuring recipient allowlists for security, email reading/searching/threading, attachments, drafts, folder management, and sending/reply tools.
      MIT

    • MCP Email Server with SendGrid

      wojkos
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI applications to send text, HTML, and template-based emails using SendGrid. It supports file attachments, CC/BCC recipients, and easy deployment via Python or Docker.
      -
    • fagents-mcp by fagents

      fagents-mcpofficial

      fagents
      A
      license
      Not graded
      quality
      C
      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

    • CronGrid

      chaser164
      A
      license
      A
      quality
      D
      maintenance
      This MCP server enables LLMs to POST, GET, and DELETE cron jobs that schedule email sends via SendGrid.
      4
      1
      MIT

    • gmail-mcp

      klodr
      A
      license
      Not graded
      quality
      A
      maintenance
      Gmail MCP server — scope-gated tools (readonly / send / modify), path jails for attachments + downloads, hardened OAuth credentials, Sigstore-signed releases.
      133 npm
      12
      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.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operation: preview vs send, add vs remove suppression, list vs get template, list vs check suppression. Even the two-step email flow is clearly separated by intent and confirm token. No overlapping purposes.

    Naming Consistency4/5

    Most tools follow verb_noun (preview_email, add_suppression, list_templates, check_suppression) with consistent use of list/get for collections vs single items. 'server_status' is the only deviation, using noun_noun instead of a verb.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range. Each tool covers a meaningful part of email sending, suppression management, templates, stats, and domain auth. The count feels intentional and scoped, not padded or sparse.

    Completeness4/5

    Covers the core workflows: preview-and-send, suppression management (add/remove/list/check), template inspection, stats, and domain auth. Minor gaps exist (no template creation/update/delete, no per-template stats), but they don't block the primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources