Skip to main content
Glama
arkaigrowth

Gmail MCP Server

by arkaigrowth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Gmail MCP Server

No user-submitted related servers found.

    Related Servers

    • Gmail MCP Server

      navbuildz
      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.
      132 npm
      13
      MIT

    • gmail-mcp

      Nicolasza1973
      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

    • Gmail MCP

      ykuchiki
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to send, read, search, and manage Gmail emails, drafts, and labels via the Model Context Protocol.
      5
      MIT

    • Gmail MCP Server

      simiancraft
      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.
      132 npm
      3
      MIT

    • multiGmailMCP

      santoshachari
      F
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to multiple Gmail accounts simultaneously, enabling search, read, draft, send, and reply operations with per-account permission controls.
      54
      -
    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

    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

    ActivityStale
    ResponsivenessNo issues

    Resources