Skip to main content
Glama
dtaveeva

gmail-multi-mcp

by dtaveeva

Related Servers

Alternatives to gmail-multi-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      C
      quality
      D
      maintenance
      Multi-account Gmail MCP server that lets assistants scan inbox, read threads, draft and send emails only after human approval, and manage follow-up reminders.
      42
      45 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects Gmail and Google Calendar to AI assistants, enabling email search, reading, sending, and calendar management across multiple accounts with secure OAuth.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A high-performance MCP server that enables AI assistants to interact with Gmail securely via OAuth 2.0, supporting smart email retrieval and thread-aware drafting.
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI assistants access Gmail, Drive, Docs, and Calendar across multiple Google accounts, routing each request by a human-readable account alias. It supports reading, searching, and writing with per-account tagging while keeping OAuth credentials secure and separate.
      -
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that provides an email operating system for AI agents, enabling inbox triage and reply drafting while enforcing un-bypassable safety constraints on sensitive actions like money transfers and banking changes.
      12
      61 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are distinct with clear purposes: search, read, send, trash, and label operations each target different actions. gmail_send and gmail_send_draft are related but clearly separated by drafting vs. sending existing drafts, and the preview/confirm flow further differentiates them.

    Naming Consistency4/5

    All tools use snake_case with a gmail_ prefix and generally follow a verb_noun pattern (list_accounts, read_message, modify_labels). Minor deviations like gmail_search and gmail_send omit a noun, but the pattern remains readable and consistent.

    Tool Count5/5

    10 tools is well within the ideal range for a domain-specific server. Each tool covers a core Gmail operation—search, read, draft, send, label, trash—and none feel redundant or bloaty.

    Completeness4/5

    Core Gmail workflows are covered, including search, read, draft, send, label modification, and trash. Minor gaps like label creation, reply/forward, and attachment handling exist, but permanent deletion is intentionally excluded, and the surface covers the common lifecycle well.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues