mcp-gdrive MCP Server

The mcp-gdrive server integrates with Google Drive to enable file management and data manipulation via the Model Context Protocol (MCP). It allows users to list, read, and search files, and provides specific capabilities for interacting with Google Sheets and Google Docs.

Key capabilities include:

• File Search: Locate files within Google Drive.
• File Reading: Access contents of various file types.
• Google Sheets Integration: Read data from spreadsheets and update specific cell values.
• Automatic Exporting: Google Workspace files are automatically converted for easier consumption:
  • Docs $\rightarrow$ Markdown
  • Sheets $\rightarrow$ CSV
  • Presentations $\rightarrow$ Plain text
  • Drawings $\rightarrow$ PNG

The server provides access to Google Drive files via a custom URI scheme. You can reference files using the following format:

gdrive:///<file_id>

This resource access supports all file types. As noted in the overview, Google Workspace files are automatically exported to compatible formats (Markdown, CSV, Plain text, or PNG) when accessed this way.

To use the Google Drive MCP server within an MCP-compatible desktop application, add the following configuration to your mcpServers settings. Ensure you replace the placeholders with your actual credentials and paths.

{
  "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"
      }
    }
  }
}

The server exposes various tools through the ListToolsRequestSchema and CallToolRequestSchema handlers.

To use a tool:

1. Call ListToolsRequestSchema to discover available tool names, descriptions, and their inputSchema.
2. Call CallToolRequestSchema with the desired name and the required arguments.

The server handles authentication automatically before executing tools via ensureAuth().

The mcp-gdrive server implements the Model Context Protocol (MCP) to provide access to Google Drive via a standard interface. It exposes two primary capabilities:

1. Resources: It uses the gdrive:/// URI scheme to represent files. Users can list available files and read their contents.
2. Tools: It provides a set of tools (defined in the tools module) that allow for more complex interactions with the Drive API.

The server uses StdioServerTransport for communication and requires valid Google credentials, which it manages via ensureAuth and setupTokenRefresh to handle token lifecycles automatically.

The server supports the gdrive:/// URI scheme for interacting with files as resources:

• Listing Resources: When ListResourcesRequestSchema is called, the server returns a list of files with their uri (formatted as gdrive:///{fileId}), mimeType, and name. It supports pagination via the cursor parameter.
• Reading Resources: When ReadResourceRequestSchema is called with a URI like gdrive:///FILE_ID, the server retrieves the file content. Note that the current implementation specifically extracts text content by skipping the Contents of file: prefix provided by the internal tool response.

The server exposes the following tools for interacting with Google Drive and Google Sheets:

Drive Tools

• gdrive_search: Search for files.
  • Inputs: query (string), pageToken (string, optional), pageSize (number, optional, max 100).
  • Output: File names and MIME types.
• gdrive_read_file: Read file contents.
  • Inputs: fileId (string).
  • Output: File contents.

Sheets Tools

• gsheets_read: Read spreadsheet data.
  • Inputs: spreadsheetId (string), ranges (array of strings, optional, e.g., ['Sheet1!A1:B10']), sheetId (number, optional).
  • Output: Spreadsheet data.
• gsheets_update_cell: Update a single cell.
  • Inputs: fileId (string), range (string, e.g., 'Sheet1!A1'), value (string).
  • Output: Confirmation of the updated value.

The tools array exports all available Model Context Protocol (MCP) tools provided by this server. Each tool object contains a schema (defining its name, description, and input parameters) and a handler function that executes the tool logic.

Available tools:

• gdrive_search (via search)
• gdrive_read_file (via readFile)
• gsheets_update_cell (via updateCell)
• gsheets_read (via readSheet)

import { tools } from './tools/index.js';

// The tools array contains Tool objects with schemas and handlers
for (const tool of tools) {
  console.log(tool.name);
  console.log(tool.inputSchema);
}

The server uses a custom URI scheme to identify Google Drive files:

• Scheme: gdrive:///
• Format: gdrive:///{file_id}