Google Drive MCP Server
Related Servers
Alternatives to Google Drive MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to list, read, create, and manage files in Google Drive. It features automatic conversion of Google Workspace formats into Markdown, CSV, and plain text for seamless integration with AI workflows.35 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides tools to search, list, and read files from Google Drive.MIT
- -licenseNot gradedqualityAmaintenanceThis MCP server integrates with Google Drive to allow listing, reading, and searching over files.3,198 npm90,196MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables interaction with Google Drive through the Google Cloud API. It allows users to list, read, and upload files directly from MCP-compatible clients like manus.im or Cursor.-
- AlicenseNot gradedqualityDmaintenanceA server that provides a Machine Control Protocol (MCP) interface to search, access, and interact with Google Drive files and folders, enabling AI assistants to work with Google Drive content.8MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides secure integration with Google Drive, Docs, Sheets, Slides, and Calendar, enabling file management and calendar operations through natural language.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_file_info retrieves detailed metadata for a specific file by ID, while list_files enumerates files from Google Drive. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on whether it needs information about a single file or a list of files.
Both tools follow a consistent verb_noun naming pattern (get_file_info and list_files), using snake_case and clear, descriptive verbs. This consistency makes the tool set predictable and easy to understand at a glance.
With only two tools, this server feels severely under-scoped for a Google Drive integration. Basic operations like uploading, updating, deleting, or searching files are missing, which limits the server's utility and suggests an incomplete implementation for the domain.
The tool set is severely incomplete for a Google Drive server. It lacks essential CRUD operations (e.g., upload_file, update_file, delete_file), search capabilities, folder management, and sharing functions. Agents will face dead ends when trying to perform common Drive tasks beyond listing and getting file info.