Skip to main content
Glama
wildfly8

Google Drive Agentic Retrieval MCP

by wildfly8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Google Drive Agentic Retrieval MCP

No user-submitted related servers found.

    Related Servers

    • google-drive-rag-mcp

      asamiile
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server that enables LLMs to securely search and read files within designated Google Drive folders. Supports Google Docs, Google Sheets, PDFs, and plain text with strict folder-scoping via service account authentication.
      4
      MIT

    • Google Drive MCP Server

      wagnerlabs
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only Model Context Protocol server that enables LLMs to search, list, and read files from Google Drive and shared drives. It automatically converts Google Workspace documents like Docs, Sheets, and Slides into Markdown, CSV, and plain text formats for easy processing.
      8 npm
      MIT

    • mcp-server-drive

      apercura
      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.
      13 npm
      2
      -

    • akij-hr-data-mcp

      mdshahabdulaziz-beep
      F
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes a configured Google Drive folder to MCP clients, enabling them to list, search, and extract content from various file formats like Excel, CSV, PDF, DOCX, and images.
      -

    • mise-en-space

      spm1001
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables LLMs to search, fetch, and act on Google Workspace (Drive, Gmail, Docs, Sheets, etc.) with rich, one-call results and file deposits to disk, reducing context usage.
      3
      MIT
    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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: drive_find for filename-stem discovery, drive_ls for one-level folder listing, drive_read for fetching a known file's body, and drive_grep for exact content matching. The descriptions include explicit cross-references ('When not to use') pointing to the correct alternative tool, eliminating misselection.

    Naming Consistency5/5

    All four tools share the same drive_ prefix with a short verb (find, ls, read, grep) in consistent snake_case. 'ls' is a conventional abbreviation rather than a convention break, so the pattern is fully predictable.

    Tool Count5/5

    Four tools is a tight, well-scoped set for a read-only retrieval server, and each one earns its place (discover by name, list a folder, read a file, grep contents). No redundant or filler tools.

    Completeness4/5

    For a retrieval-only domain the surface covers discovery, navigation, body reading, and content search, with no obvious dead ends. Minor gap: drive_find can return PARTIAL but exposes no continuation cursor, unlike ls and grep, so a capped filename walk must be re-run.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources