Skip to main content
Glama
A1-x-Tech

A1 Gmail MCP

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to A1 Gmail MCP

No user-submitted related servers found.

    Related Servers

    • Gmail AutoAuth MCP Server

      lowrykun
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Gmail through natural language, including sending, reading, searching, labeling emails, managing attachments, and performing thread operations.
      3
      MIT

    • Gmail AutoAuth MCP Server

      StephenLReed
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Gmail through natural language interactions, including sending, reading, searching emails, and managing labels with auto authentication support.
      22,687 npm
      1
      MIT

    • Gmail AutoAuth MCP Server

      cgutiguti
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage Gmail through natural language interactions with auto-authentication, including sending, reading, searching, and organizing emails and labels.
      22,687 npm
      MIT

    • gmail-mcp

      hahaha-saygex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Gmail emails, including sending, searching, and organizing with labels and attachments via OAuth2.
      56 npm
      2
      MIT

    • gmail-mcp

      leadborg
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to send, read, list, and reply to emails via the Gmail API.
      Apache 2.0
    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.3/5.0

    Scored across 24 tools

    Disambiguation4/5

    Tools mostly have clearly distinct purposes, but there are intentional overlaps between message-level and thread-level operations (get_message/get_thread, modify_message/modify_thread, list_messages/list_threads, send_message/send_draft, delete_draft/manage_trash). The descriptions explain when to use which, so selection is guided, though the parallel message/thread pairs invite occasional misselection.

    Naming Consistency5/5

    A consistent verb_noun snake_case pattern runs throughout (start_login, list_messages, get_thread, create_draft, update_draft, send_message, modify_thread, manage_trash, manage_labels). Only raw_request deviates, which is reasonable as an escape hatch.

    Tool Count3/5

    24 tools is on the heavy side and includes near-parallel message/thread and draft/auth groups that could be trimmed. For a full Gmail client with auth, labels, and both message and thread operations, most tools are justified, but the count is borderline.

    Completeness5/5

    The surface covers the full Gmail lifecycle: auth (start/auth/setup/set_client/finish/logout), profile, message and thread CRUD, sending, drafts, labels, trash with a deliberate no-permanent-delete safety net, and raw_request for anything uncovered. Coverage is comprehensive for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources