Skip to main content
Glama

Related Servers

Alternatives to drive-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an MCP client to search, read, label, draft, and send Gmail messages for a single Google account over stdio using your own OAuth client.
      89 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local, read-only MCP server for searching your Google Drive.
      11 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A read-only Google Drive MCP server that allows searching files, reading file content (with auto-export for Google Docs, Sheets, Slides), and retrieving file metadata via OAuth authentication.
      15 npm
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local stdio MCP server that handles Google OAuth2 locally and proxies authenticated requests to Google Docs and Google Drive REST APIs, enabling document and file operations from Cursor or other MCP clients.
      49 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: separate tools for creating folders vs files, reading content vs downloading, updating content vs metadata, and sharing vs unsharing. Overlaps like list_folder/search_files/list_recent_files are clearly distinguished by scope and filters.

    Naming Consistency5/5

    All tools use snake_case with a consistent verb_noun pattern (e.g., create_folder, update_file_content, share_file). Variations like list_recent_files and get_file_metadata are still predictable and readable.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range but justified by Google Drive's breadth (files, folders, permissions, sharing, trash, content I/O). No tool appears redundant, though a few could theoretically be merged.

    Completeness4/5

    Core lifecycle is covered: create, read, update, copy, trash/untrash, share/unshare. Minor gaps include no permanent delete (trash is reversible) and no dedicated move operation (handled via update_file_metadata), but no critical dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues