Google Drive MCP Server

Created By
asadudina year ago
A Model Context Protocol (MCP) server for interacting with Google Drive API
Overview

what is Google Drive MCP Server?

Google Drive MCP Server is a Model Context Protocol (MCP) server designed to interact with the Google Drive API, providing a standardized interface for AI systems to access and manipulate files in Google Drive.

how to use Google Drive MCP Server?

To use the Google Drive MCP Server, set up the server and connect it to your Google Drive account. You can then perform various file operations through the provided API endpoints.

key features of Google Drive MCP Server?

  • File Operations: List, upload, download, and delete files.
  • Folder Management: Create folders and organize content.
  • File Sharing: Share files with specific users and manage permissions.
  • Pagination Support: Efficiently handle large file listings.
  • Comprehensive Error Handling: Detailed error reporting for easier debugging.

use cases of Google Drive MCP Server?

  1. Automating file uploads and downloads for AI applications.
  2. Managing shared documents in collaborative projects.
  3. Organizing files and folders programmatically for better data management.

FAQ from Google Drive MCP Server?

  • Can I use this server for any Google Drive account?

Yes! The server can be connected to any Google Drive account with the appropriate permissions.

  • Is there a limit to the number of files I can manage?

The server can handle large file listings, but Google Drive API limits may apply.

  • How do I handle errors when using the server?

The server provides comprehensive error handling and detailed error messages to assist with debugging.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
asadudin
Star
0
Language
Python
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