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

JavaScript
a year ago
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)

5 hours ago