Drive

This MCP server lets you interact with Google Drive and Google Sheets from your MCP client. You can list and read files, search Drive, and read or update data in Google Sheets, all through a single configurable server that you run alongside your app.

How to use

You connect to the Google Drive MCP server from your MCP client by configuring an MCP server entry in your client’s server list. Once connected, you can search for files on Google Drive, read file contents, and read or update data in Google Sheets. When you start the server for the first time, you will be prompted to authenticate with a Google account that has access to your project’s Drive and Sheets resources. Your OAuth token will be stored in the directory you designate for credentials.

Typical tasks you can perform include:

• Searching Drive for files by query
• Reading the contents of a Drive file by its ID
• Reading data from a Google Spreadsheet with optional ranges
• Updating a cell in a Google Spreadsheet by specifying a range and value These actions are exposed as MCP endpoints through the gdrive MCP server and will appear as endpoints in your MCP client once the server is running and configured.

How to install

Prerequisites you need before installation:
- Node.js and npm installed on your machine
- A Google Cloud project with Drive and Sheets APIs enabled
- A configured OAuth client for a Desktop App and the corresponding credentials file
- A local directory where you will store OAuth credentials (GDRIVE_CREDS_DIR)

Step-by-step setup and run flow:
1. Create a new Google Cloud project
2. Enable the Google Drive API and Google Sheets API
3. Configure an OAuth consent screen (internal is fine for testing)
4. Add OAuth scopes for Drive and Sheets:
   - https://www.googleapis.com/auth/drive.readonly
   - https://www.googleapis.com/auth/spreadsheets
5. Create an OAuth Client ID for application type Desktop App
6. Download the JSON file containing your client’s OAuth keys
7. Rename the key file to gcp-oauth.keys.json and place it in your credentials directory (the path you configure as GDRIVE_CREDS_DIR)
8. Note your OAuth Client ID and Client Secret; you will provide these as environment variables when you run the server
9. Build or watch the MCP server before running:
   - npm run build
   - or npm run watch

Configuration and start example

To run the Google Drive MCP server alongside your desktop MCP app, configure your client to load the server using an MCP entry like this. Replace the placeholder values with your actual IDs and the path to your credentials directory.

{
  "mcpServers": {
    "gdrive": {
      "command": "npx",
      "args": [
        "-y",
        "@isaacphi/mcp-gdrive"
      ],
      "env": {
        "CLIENT_ID": "<CLIENT_ID>",
        "CLIENT_SECRET": "<CLIENT_SECRET>",
        "GDRIVE_CREDS_DIR": "/path/to/config/directory"
      }
    }
  }
}

Security and notes

Security: You must authenticate with a Google account that has access to your Google Cloud project resources. OAuth tokens are stored in the directory you specify via GDRIVE_CREDS_DIR. Protect this directory and avoid exposing your CLIENT_ID, CLIENT_SECRET, or credentials file publicly.

Available tools

gdrive_search

Search for files in Google Drive by a query and return matching file names and MIME types.

gdrive_read_file

Read the contents of a Google Drive file by its fileId.

gsheets_read

Read data from a Google Spreadsheet with optional ranges and sheet selection.

gsheets_update_cell

Update a specific cell in a Google Spreadsheet by its A1 range and value.