Skip to main content
Glama
Sign In
Google Drive MCP Server

Google Drive MCP Server

by pedrohzwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Google Drive MCP Server

This is a simple MCP server that integrates with Google Drive.

Prerequisites

  1. Node.js: Version 18 or higher is recommended (the current environment is using 16, so you might need to upgrade for full compatibility).

  2. Google Cloud Project:

    • Go to the Google Cloud Console.

    • Create a project.

    • Enable the Google Drive API.

    • Create a Service Account and download the JSON key file.

  3. Authentication:

    • Set the environment variable GOOGLE_APPLICATION_CREDENTIALS to the path of your JSON key file.

    • Alternatively, share the folder/files you want to access with the service account's email address.

Related MCP server: Google Drive MCP Server

Configuration for Claude Desktop

Add the following to your Claude Desktop configuration file:

Windows: %APPDATA%\Claude\claude_desktop_config.json macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "google-drive": {
      "command": "node",
      "args": [
        "c:/git/projects/drive-mcp-connect/build/index.js"
      ],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "C:/path/to/your/service-account-key.json"
      }
    }
  }
}

Tools Provided

  • list_files: List files in your Google Drive.

  • get_file_info: Get metadata for a specific file by its ID.

Available Tools

2 tools
get_file_infoB

Get detailed information about a specific file by ID

Inputs: fileId (required).

list_filesC

List files from Google Drive

Inputs: pageSize, q.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness1/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers