Google Drive MCP
UpGoogle Drive MCP is Google's official server for Drive (Developer Preview): 8 tools like search_files, read_file_content and get_file_permissions give an agent natural-language file search, reading and copying instead of manual folder navigation. A single endpoint over JSON-RPC on HTTPS, auth via Google OAuth 2.0. Available under the Google Workspace Developer Preview program.
Why this server
- Google's official Drive MCP (Developer Preview) — search and read files with no manual download
- 8 tools: search_files, read_file_content, get_file_permissions and more
- JSON-RPC over HTTPS on one global endpoint — no regional differences
- get_file_permissions lets the agent check who else has access before sharing data
Usage examples
Prompt: Find the Rebranding project deck and show who has access to it
Result: The agent called search_files by title, then get_file_permissions on the match — returning the list of users with access.
Prompt: Copy the contract template into my Legal folder and open the text for editing
Result: The agent called copy_file to duplicate the template, then read_file_content — the contract text arrived right in chat for editing.
Health
120 reports in the last 30 days · Last report: 22 Sept 2026
Reports by day (30 days)
| date | works | partial | broken |
|---|---|---|---|
| 2026-08-24 | 4 | 0 | 0 |
| 2026-08-25 | 4 | 0 | 0 |
| 2026-08-26 | 4 | 0 | 0 |
| 2026-08-27 | 4 | 0 | 0 |
| 2026-08-28 | 4 | 0 | 0 |
| 2026-08-29 | 4 | 0 | 0 |
| 2026-08-30 | 4 | 0 | 0 |
| 2026-08-31 | 4 | 0 | 0 |
| 2026-09-01 | 4 | 0 | 0 |
| 2026-09-02 | 4 | 0 | 0 |
| 2026-09-03 | 4 | 0 | 0 |
| 2026-09-04 | 4 | 0 | 0 |
| 2026-09-05 | 4 | 0 | 0 |
| 2026-09-06 | 4 | 0 | 0 |
| 2026-09-07 | 4 | 0 | 0 |
| 2026-09-08 | 4 | 0 | 0 |
| 2026-09-09 | 4 | 0 | 0 |
| 2026-09-10 | 4 | 0 | 0 |
| 2026-09-11 | 4 | 0 | 0 |
| 2026-09-12 | 4 | 0 | 0 |
| 2026-09-13 | 4 | 0 | 0 |
| 2026-09-14 | 4 | 0 | 0 |
| 2026-09-15 | 4 | 0 | 0 |
| 2026-09-16 | 4 | 0 | 0 |
| 2026-09-17 | 4 | 0 | 0 |
| 2026-09-18 | 4 | 0 | 0 |
| 2026-09-19 | 4 | 0 | 0 |
| 2026-09-20 | 4 | 0 | 0 |
| 2026-09-21 | 4 | 0 | 0 |
| 2026-09-22 | 2 | 0 | 0 |
Server tools · 8
Collected by auto-check from tools/list — the real list, not the description.
copy_fileCall this tool to copy an existing File in Google Drive. The tool allows specifying a new title and a parent folder for the copy. If the title is not specified, the copy title will be 'Copy of {original title}'. If the parent folder is not specified, the copy will be created in the same folder as the original file, unless the requesting user does not have write access to that folder, in which case the copy will be created in the user's root folder.Returns the newly created File object upon successful copying.
create_fileCall this tool to create or upload a File to Google Drive. If uploading content, prefer `textContent` for text content. For non-UTF8 contents, use the `base64Content` field and base64 encode the data to set on that field. Returns a single File object upon successful creation. The following Google first-party mime types can be created without providing content: - `application/vnd.google-apps.document` - `application/vnd.google-apps.spreadsheet` - `application/vnd.google-apps.presentation` Folders can be created by setting the mime type to `application/vnd.google-apps.folder`. When uploading content, the `contentMimeType` field is required and should match the type of the content being uploaded. By default, supported content will be converted to Google first-party mime types. To disable conversions for first-party mime types, set `disableConversionToGoogleType` to true.
download_file_contentCall this tool to download the content of a Drive file as a base64 encoded string. If the file is a Google Drive first-party mime type, the `exportMimeType` field specifies the desired export mime type. When the field is unset, defaults to plain text types (e.g. `text/plain`, `text/csv`). If the file is not found, try using other tools like `search_files` to find the file the user is requesting. If the user wants a natural language representation of their Drive content, use the `read_file_content` tool (`read_file_content` should be smaller and easier to parse).
get_file_metadataCall this tool to find general metadata about a user's Drive file. Context window token management can be tuned via `snippetVerbosity` (default is `SnippetVerbosity.DETAILED`) or if only metadata is needed, use `excludeContentSnippets`. If the file is not found, try using other tools like `search_files` to find the file the user is requesting.
get_file_permissionsCall this tool to list the permissions of a Drive File.
list_recent_filesCall this tool to find recent files for a user specified a sort order. Default sort order is `recency` if orderBy is not set or set to an unsupported value. Context window token management can be tuned via `snippetVerbosity` (default is `SnippetVerbosity.DETAILED`) or if only metadata is needed, use `excludeContentSnippets`. Supported sort orders are: - `recency`: The most recent timestamp from the file's date-time fields. - `lastModified`: The last time the file was modified by anyone. - `lastModifiedByMe`: The last time the file was modified by the user. The default page size is 10. Utilize `next_page_token` to paginate through the results.
read_file_contentCall this tool to fetch a natural language representation of a known Drive file, and if specified, its comments. REQUIREMENTS & WORKFLOW: - `fileId` is required. You MUST pass an exact Drive file ID returned by a previous discovery tool (`search_files` or `list_recent_files`) or provided explicitly in the user prompt. - NEVER guess, invent, or hallucinate a `fileId` string from a file title or name. - If given a file title, name, or topic without an explicit `fileId`, you MUST FIRST call `search_files` to find the file and retrieve its `fileId` before invoking this tool. The file content may be incomplete for very large files. The text representation will change over time, so don't make assumptions about the particular format of the text returned by this tool. If supported and specified, comment tags will be included in the content. Supported Mime Types: - `application/vnd.google-apps.document` (supports comments) - `application/vnd.google-apps.presentation` (supports comments
search_filesSearch for Drive files using a structured query (syntax: `query_term operator values`). Only terms in this list are supported. Combine clauses with `and`, `or`, `not`, and parentheses. String values must be single-quoted; escape embedded quotes as `\'`. Context window token management can be tuned via `snippetVerbosity` (default is `SnippetVerbosity.DETAILED`) or if only metadata is needed, use `excludeContentSnippets`. Do NOT include document type terms (e.g., 'presentation', 'slides', 'deck', 'document', 'doc', 'spreadsheet', 'sheet', 'pdf', 'folder') inside `title contains '...'` or `fullText contains '...'` clauses. Separate title keywords from file type terms. Instead map them to `mimeType` clauses in the query (e.g., 'slides' -> `mimeType = 'application/vnd.google-apps.presentation'`). Query terms & operators: - `title` (ops: contains, =, !=) — file title - `fullText` (ops: contains) — title or body text - `mimeType` (ops: contains, =, !=) — MIME type - `modifiedTime`, `vi
Reviews
No reviews yet.