McpGoogleDrive

Created By
achrafhardizia year ago
MCP server that manages Google Drive
Overview

what is McpGoogleDrive?

McpGoogleDrive is a Spring Boot application that provides a set of RESTful API endpoints to manage Google Drive operations such as listing files, getting file details, searching files, creating folders, and downloading files as PDF.

how to use McpGoogleDrive?

To use McpGoogleDrive, clone the repository, build the project using Gradle, and configure the Google Drive API credentials. You can then access the API endpoints to perform various operations on Google Drive.

key features of McpGoogleDrive?

  • List files in Google Drive
  • Get details of a specific file
  • Search files by name
  • Create folders in Google Drive
  • Download files as PDF

use cases of McpGoogleDrive?

  1. Automating file management tasks in Google Drive.
  2. Integrating Google Drive functionalities into other applications.
  3. Creating a custom file management interface for users.

FAQ from McpGoogleDrive?

  • What are the prerequisites to run McpGoogleDrive?

You need Java 17 or higher, Gradle, a Google Cloud Platform account, Google Drive API enabled, and service account credentials JSON file.

  • Is McpGoogleDrive free to use?

Yes! McpGoogleDrive is free to use as it is an open-source project.

  • How do I configure the Google Drive API?

You need to set up a project in the Google Cloud Console, enable the Google Drive API, create a service account, and provide the credentials in the application properties.

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