# Google Drive [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/mcp-z/mcp-drive#readme  
**GitHub Stars:** 1  
**npm Downloads (last month):** 555  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-drive-2

## Description
Google Drive integration with file operations, folder navigation, search, and sharing

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "google-drive": {
    "command": "npx",
    "args": ["-y","@mcp-z/cli"],
    "env": {
      "GOOGLE_CLIENT_ID": "",
      "GOOGLE_CLIENT_SECRET": "",
      "REDIRECT_URI": "",
      "AUTH_MODE": "",
      "GOOGLE_SERVICE_ACCOUNT_KEY_FILE": "",
      "TOKEN_STORE_URI": "",
      "DCR_STORE_URI": ""
    }
  }
}
```

**Requires environment variables:** `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`, `REDIRECT_URI`, `AUTH_MODE`, `GOOGLE_SERVICE_ACCOUNT_KEY_FILE`, `TOKEN_STORE_URI`, `DCR_STORE_URI` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Google Drive MCP server does

The Google Drive MCP server exposes selected Google Drive operations as MCP tools. Agents can search for files and folders, inspect the contents of a folder, resolve folder paths, create folders, move items, move items to the trash, and upload files. Uploads can use either a local path or a URL.

The package also exposes a `file` resource and two prompts: `organize-files` and `query-syntax`. The latter can help clients work with Drive search syntax. The available tools are `file-move`, `file-move-to-trash`, `file-upload`, `files-search`, `folder-contents`, `folder-create`, `folder-path`, and `folder-search`.

## How it works

The Google Drive MCP server supports both stdio and HTTP transports. A local MCP client can start it with `npx -y @mcp-z/mcp-drive`, while an HTTP deployment can run the package with a port such as `9001` and expose its MCP endpoint at `/mcp`. The `start` block shown in the configuration examples is handled by `@mcp-z/cli up`; it is not a separate server feature.

Clients negotiate between the supported 2025 and 2026-07-28 MCP protocol revisions. The newer revision is stateless, while clients using the 2025 revision continue to use the normal initialization behavior.

After startup, Google authorization is required before calling Drive tools. The default loopback OAuth flow uses a Google Cloud project, an enabled Drive API, OAuth credentials, and the requested Drive and identity scopes. Service-account authentication is also available. Dynamic client registration is supported for HTTP deployments with a public base URL.

## Setup and configuration

Install Node.js 20 or newer. In Google Cloud Console, create or select a project, enable the Google Drive API, create OAuth credentials, configure the required scopes, and add test users when the application is in testing mode.

For default OAuth, provide `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET`. Local use can omit `REDIRECT_URI` and use an ephemeral loopback callback. A hosted deployment can set `REDIRECT_URI` to its public OAuth callback. Service-account mode uses `AUTH_MODE=service-account` and `GOOGLE_SERVICE_ACCOUNT_KEY_FILE`.

Token and DCR registration data use Keyv storage URIs. `file://` is the default, and `memory://` is available without another adapter. Other protocols require the corresponding Keyv adapter to be installed.

## Tools and capabilities

- Search files and folders with Drive query syntax.
- List the contents of a folder and inspect folder paths.
- Create folders and move existing Drive items.
- Send items to the Drive trash.
- Upload files from a local filesystem path or URL.
- Inspect the server's tools with `npx -y @mcp-z/cli inspect --servers drive --tools`.
- Invoke a tool through `@mcp-z/cli call-tool` after authorization.

## Limitations and notes

OAuth and service-account access depend on Google Cloud configuration and the permissions available to the selected account. DCR mode is HTTP-only and requires a public base URL. The complete environment-variable and command-line configuration is maintained in `server.json`.

_Full upstream README: https://allmcps.com/mcp/google-drive-2/readme_