Skip to main content
Glama
Schneckenhausmann

google-nice-mcp

by Schneckenhausmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to google-nice-mcp

No user-submitted related servers found.

    Related Servers

    • Proton MCP

      lucasoishi
      A
      license
      Not graded
      quality
      C
      maintenance
      A local, read-only MCP server that lets an AI agent search and read Proton Mail and Proton Drive, connecting to Mail through Proton Mail Bridge over IMAP and to Drive through the desktop app's synced folder. It exposes tools for listing folders, searching messages, reading mail bodies and attachments, and browsing or reading files from Drive, without ever writing, sending, or changing anything.
      MIT

    • Gmail MCP Server

      jlg-formation
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Gmail that enables searching threads, reading messages, and listing labels without any write access.
      174 npm
      MIT

    • Gmail MCP Gateway

      systheno
      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

    • gmail-research-mcp

      bajor
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only Gmail MCP server that searches email, fetches complete threads, and stores them as local Markdown and JSON for offline analysis by other agents.
      1
      -
    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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Tools are clearly separated by service prefix (drive_ vs gmail_) and have distinct purposes: listing drives, searching and reading files, searching and reading emails. No overlap in functionality.

    Naming Consistency4/5

    All tools follow a service_verb[_object] pattern with underscores, but some use a bare verb (drive_search, gmail_search) while others include an object (drive_list_shared_drives, drive_read_file, gmail_read_email). Slight inconsistency but the pattern is predictable.

    Tool Count5/5

    With 5 tools covering two Google services, the count is well-scoped. Each tool serves a clear purpose and there is no bloat or deficiency for the apparent scope.

    Completeness3/5

    The server covers search and read operations for both Drive and Gmail, but lacks any write or update capabilities (e.g., create, delete, send). This is a notable gap that may require additional tools for full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources