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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

35 minutes ago