1. Conduid
  2. Productivity
  3. Gdrive MCP Server
MCP server · Productivity

Gdrive MCP Server

Google Drive MCP Server

Unclaimed last commit 10 months ago productivity
43Fair

Scored 5 months ago · breakdown

About Gdrive MCP Server

Gdrive MCP Server is an MCP server published by ankitpyc in the Productivity category: google Drive MCP Server.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/ankitpyc/gdrive-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Gdrive MCP Server

Powered by Claude · Grounded in docs

I know everything about Gdrive MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

Google Drive MCP Server ☁️

Go Reference

This project implements a Model Context Protocol (MCP) server that provides tools and resources for interacting with Google Drive. It allows for programmatic access to Google Drive functionalities, enabling other MCP-compatible agents or systems to manage files and folders.

Table of Contents

Current Features ✨

The server currently provides the following functionalities:

  • File and Folder Listing 📂: List files and folders within a specified Google Drive folder, including the root.
  • File Creation 📄: Create new files with specified content in a given Google Drive path.
  • DOCX File Creation 📝: Create new .docx files with specified content in a given Google Drive path.
  • Folder Suggestion 💡: Suggests a Google Drive folder based on the content name.

Project Structure 🏗️

The project follows a standard Go project layout:

  • cmd/server/: Contains the main application entry point for the MCP server.
  • configs/: Stores configuration files, such as the Google Service Account credentials.
  • internal/: Reserved for private application and library code that should not be imported by other applications.
  • pkg/driveapi/: Contains reusable library code for interacting with the Google Drive API. This includes client setup, file operations, folder management, and suggestion logic.

Setup Instructions 🛠️

To set up and run the Google Drive MCP Server, follow these steps:

Prerequisites ✅

  • Go (version 1.18 or higher)
  • Docker or Podman (for running the MCP server)
  • Google Cloud Project with Google Drive API enabled
  • Service Account Key (JSON file) for authentication with Google Drive API

Configuration ⚙️

  1. Enable Google Drive API:

    • Go to the Google Cloud Console.
    • Create a new project or select an existing one.
    • Navigate to "APIs & Services" > "Library".
    • Search for "Google Drive API" and enable it.
  2. Create a Service Account:

    • In the Google Cloud Console, go to "APIs & Services" > "Credentials".
    • Click "Create Credentials" > "Service Account".
    • Follow the steps to create a new service account.
    • Grant the service account appropriate roles (e.g., "Drive File Organizer" or "Drive Editor") to access Google Drive.
  3. Generate a Service Account Key:

    • After creating the service account, click on its email address.
    • Go to the "Keys" tab and click "Add Key" > "Create new key".
    • Select "JSON" as the key type and click "Create".
    • A JSON file will be downloaded. Rename it to credentials.json and place it in the configs/ directory of this project.
  4. Share Google Drive Folders/Files with Service Account:

    • The service account needs explicit access to the Google Drive folders/files it will interact with. Share the relevant folders/files with the service account's email address (found in the credentials.json file).

Running the Server 🚀

  1. Build the Docker Image:

    docker build -t gdrive-mcp-server .
    

    or

    podman build -t gdrive-mcp-server .
    
  2. Run the MCP Server:

    docker run --rm -i -e GOOGLE_APPLICATION_CREDENTIALS=/app/configs/credentials.json -v $(pwd)/configs:/app/configs gdrive-mcp-server
    

    or

    podman run --rm -i -e GOOGLE_APPLICATION_CREDENTIALS=/app/configs/credentials.json -v $(pwd)/configs:/app/configs gdrive-mcp-server
    

    Ensure that $(pwd)/configs correctly points to the directory containing your credentials.json file.

Usage 💡

Once the server is running, you can interact with it using an MCP-compatible client. The server exposes various tools for Google Drive operations. Refer to the MCP client documentation for details on how to call these tools.

Planned Features 🔮

  • File Update: Update existing files in Google Drive.
  • File Deletion: Delete files from Google Drive.
  • Folder Creation: Create new folders in Google Drive.
  • File Search: Advanced search capabilities for files based on various criteria (name, type, content).
  • Permissions Management: Manage file and folder permissions.
  • Webhooks/Notifications: Integrate with Google Drive change notifications.

Contributing 🤝

We welcome contributions to the Google Drive MCP Server! If you have suggestions, bug reports, or want to contribute code, please open an issue or submit a pull request on the GitHub repository.

License 📄

This project is licensed under the MIT License - see the LICENSE file for details.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Gdrive MCP Server

How do I install Gdrive MCP Server?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Gdrive MCP Server safe to use with an AI agent?

Its trust score is 43 out of 100 (fair). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Gdrive MCP Server still maintained?

The last commit was 10 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.