Skip to main content
Glama
bajor

gmail-mcp-send-to-list-only

by bajor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to gmail-mcp-send-to-list-only

No user-submitted related servers found.

    Related Servers

    • email-mcp

      boringfy
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for Gmail with strict alias whitelisting, allowing AI clients to search, read, reply to, and send emails only from explicitly whitelisted alias addresses while keeping all other mailbox content unreachable.
      26 npm
      ISC

    • email-mcp

      goyalayus
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that sends outbound emails with automatic single-thread mapping in Gmail, enabling reply-style conversations within a single thread.
      26 npm
      1
      MIT

    • 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
      368 npm
      MIT

    • gmail-ai-mcp

      InfiniteRoomLabs
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Gmail that provides tools to download attachments, fetch raw messages, manage filters, and create drafts, while deliberately omitting send functionality for safety.
      7
      MIT

    • Gmail MCP Gateway

      systheno
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents full read and organizational access to multiple Gmail accounts — and no ability to send, trash, or delete mail.
      MIT

    • gmail-multi-mcp

      dtaveeva
      A
      license
      A
      quality
      B
      maintenance
      MCP server that gives an AI assistant simultaneous access to multiple Gmail accounts with per-account read-only, draft, or send tiers, two-phase write confirmation, and safeguards for handling untrusted email content.
      10
      7 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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one lists allowed recipients, the other sends an email. There is no overlap in their purposes, so an agent would not confuse them.

    Naming Consistency5/5

    Both tool names follow the same pattern: 'gmail_' prefix, then a verb ('list' or 'send') and an object. This consistent snake_case naming makes the toolset predictable.

    Tool Count4/5

    With only 2 tools, the set is minimal, but the server's narrow purpose (send to a restricted list) justifies this. It is slightly under the typical 3-15 range but reasonable for the scope.

    Completeness5/5

    The domain is fully covered: the list tool lets the agent discover allowed recipients, and the send tool performs the actual email sending. No essential operations are missing for a 'send-to-list-only' server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources