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.
      13,749 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.
      13,749 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.
      47 npm
      1
      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.4/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: message-level and thread-level operations are cleanly separated, direct send vs. draft send are clearly differentiated, and modify_message/manage_trash/list_labels/manage_labels have explicit scopes. The only near-overlap, list_messages vs. list_threads, is resolved by descriptions that tell agents when to use each. No two tools are likely to be confused.

    Naming Consistency4/5

    The naming is overwhelmingly verb_noun and snake_case: list_messages, get_thread, create_draft, send_draft, delete_draft, and so on. The minor deviation is raw_request, which is a noun phrase rather than a verb_noun action. Overall the pattern is very predictable.

    Tool Count4/5

    18 tools is on the heavy side, but the count maps cleanly onto the Gmail domain: message, thread, draft, label, profile, and raw escape-hatch groups. Each tool covers a distinct operation, so the size feels comprehensive rather than bloated. It is slightly above the ideal range but still well-scoped.

    Completeness5/5

    The surface covers the full Gmail lifecycle: search/read/send/modify/trash for messages, conversation-level thread operations, draft CRUD plus send, label management, and profile info. The only missing operations, permanent delete and attachment download, are intentionally omitted for safety or covered through raw_request. There are no dead ends for common email workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources