Skip to main content
Glama
arkaigrowth

Gmail MCP Server

by arkaigrowth

Related Servers

Alternatives to Gmail MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Multi-account Gmail integration for AI agents, enabling read, write, archive, label, and auto-unsubscribe operations through the Model Context Protocol.
      269 npm
      16
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage multiple Gmail accounts in a single process through the Model Context Protocol, including cross-account search, reading threads, drafts, sending, labels, and attachments with per-account permission tiers.
      12 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Gmail to AI assistants via the MCP protocol, enabling search, read, send, and manage emails across multiple Google accounts simultaneously.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant to access and search across multiple Gmail inboxes simultaneously, allowing unified management of work, personal, and other email accounts through a single MCP server.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to send, read, search, and manage Gmail emails, drafts, and labels via the Model Context Protocol.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server for Gmail that lets AI assistants read, send, search, label, and filter Gmail through natural language, with OAuth2 auto-authentication and full attachment support.
      269 npm
      3
      MIT

    TDQS

    B3.3/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap between gmail_search_messages and gmail_search_emails, and between archive/trash workflows. Descriptions help differentiate, but ambiguity remains for agents.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern with domain prefixes (gmail_, drive_, docs_). Naming is predictable and readable across the entire set.

    Tool Count3/5

    35 tools is high, but it combines Gmail and Google Drive/Docs functionality. The count could be reduced by merging similar operations (e.g., staging/confirmation pairs), but it remains within acceptable bounds for the combined scope.

    Completeness3/5

    Common Gmail operations are covered (search, read, send, labels, filters, archive, trash), but missing permanent deletion and direct marking of read/unread. Drive/Docs coverage is basic (search, metadata, read, create, upload) but lacks editing and broader file operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues