Google Drive

Created By
isaacphi9 months ago
Overview

what is Google Drive Server?

Google Drive Server is an MCP server that integrates with Google Drive, enabling users to list, read, and search files, as well as read and write to Google Sheets.

how to use Google Drive Server?

To use the Google Drive Server, set up a Google Cloud project, enable the Google Drive and Sheets APIs, configure OAuth credentials, and run the server with the appropriate environment variables.

key features of Google Drive Server?

  • Search for files in Google Drive using specific queries.
  • Read contents of files stored in Google Drive.
  • Read and update data in Google Sheets with flexible options.

use cases of Google Drive Server?

  1. Automating file management tasks in Google Drive.
  2. Integrating Google Sheets data into applications.
  3. Building applications that require access to Google Drive files.

FAQ from Google Drive Server?

  • What APIs does this server integrate with?

The server integrates with the Google Drive API and Google Sheets API.

  • Is there a cost associated with using Google Drive Server?

The server itself is free to use, but Google Cloud services may incur costs based on usage.

  • How do I authenticate with Google Drive?

You need to set up OAuth credentials in your Google Cloud project and authenticate through the provided prompt.

Server Config

{
  "mcpServers": {
    "gdrive": {
      "command": "npx",
      "args": [
        "-y",
        "@isaacphi/mcp-gdrive"
      ],
      "env": {
        "CLIENT_ID": "850257612904-fng2g08pda1bfidtlmit4ufb972i0lvu.apps.googleusercontent.com",
        "CLIENT_SECRET": "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",
        "GDRIVE_CREDS_DIR": "/"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
7 months ago
Author Name
isaacphi
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago