Skip to main content
Glama
giantrotta24

google-mcp

by giantrotta24

Related Servers

Alternatives to google-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that manages multiple Gmail accounts simultaneously, allowing MCP clients to switch between accounts per request without logging out or in. It securely stores OAuth tokens in the macOS Keychain.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Synchronizes multiple Gmail and Google Workspace accounts into a local SQLite database and exposes search and mailbox operations through a stdio MCP interface.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Local-first Gmail MCP server using PKCE + loopback OAuth flow that stores refresh tokens in the OS keychain, enabling secure read/write Gmail access via MCP tools without tokens leaving the device.
      20
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Multi-account Gmail MCP server for reading threads, managing labels, and creating drafts across multiple Gmail accounts.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server for managing multiple Gmail accounts with separate OAuth grants, supporting search, retrieval, labels, drafts, and attachments while deferring direct send and destructive actions for safety.
      MIT

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a unique combination of service (calendar vs gmail) and account type (personal vs work), making it impossible to confuse one tool with another.

    Naming Consistency5/5

    All tools follow a strict pattern: {service}_{action}_{account}, using snake_case consistently. This makes the naming predictable and easy to understand.

    Tool Count5/5

    With 4 tools, the count is appropriate for a focused server that distinguishes between two services across two accounts, avoiding unnecessary complexity.

    Completeness3/5

    The tool set covers listing events and searching emails, but is limited to these read operations. Missing capabilities like creating or modifying events/schedules are notable gaps for a full Google workspace integration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues