Google Drive MCP Server

Created By
seeun0210a year ago
google drive mcp 서버를 만들어보자 일단 sheet부터
Overview

what is Google Drive MCP Server?

Google Drive MCP Server is a server designed to integrate with Google Drive and Google Sheets, allowing users to read and manipulate spreadsheet data.

how to use Google Drive MCP Server?

To use the server, set up a project in Google Cloud Console, enable the necessary APIs, create OAuth credentials, and run the server using npm commands.

key features of Google Drive MCP Server?

  • Integration with Google Drive and Google Sheets APIs
  • Ability to read data from Google Sheets
  • OAuth 2.0 authentication for secure access

use cases of Google Drive MCP Server?

  1. Automating data retrieval from Google Sheets for analysis.
  2. Building applications that require spreadsheet data manipulation.
  3. Creating tools that interact with Google Drive files.

FAQ from Google Drive MCP Server?

  • What APIs does this server integrate with?

It integrates with Google Drive API and Google Sheets API.

  • How do I set up the server?

Follow the setup instructions provided in the documentation, including creating a project in Google Cloud Console and configuring OAuth credentials.

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

Google Drive APIs have usage limits, but they are generally free for low usage. Check Google Cloud pricing for details.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
seeun0210
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
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.

8 hours ago