Google-Drive Universal MCP Server
This repository contains an implementation of an Google-Drive Universal MCP (Model Context Protocol) server. It provides a standardized interface for interacting with Google-Drive's tools and services through a unified API.
The server is built using the Universal MCP framework.
This implementation follows the MCP specification, ensuring compatibility with other MCP-compliant services and tools.
Usage
You can start using Google-Drive directly from agentr.dev. Visit agentr.dev/apps and enable Google-Drive.
If you have not used universal mcp before follow the setup instructions at agentr.dev/quickstart
Available Tools
The full list of available tools is at ./src/universal_mcp_google_drive/README.md
Local Development
📋 Prerequisites
Ensure you have the following before you begin:
- Python 3.11+ (recommended)
- uv (install globally with
pip install uv)
🛠️ Setup Instructions
Follow the steps below to set up your development environment:
-
Sync Project Dependencies
uv syncThis installs all dependencies from
pyproject.tomlinto a local virtual environment (.venv). -
Activate the Virtual Environment
For Linux/macOS:
source .venv/bin/activate
For Windows (PowerShell):
.venv\Scripts\Activate
-
Start the MCP Inspector
mcp dev src/universal_mcp_google_drive/server.py
This will start the MCP inspector. Make note of the address and port shown in the console output.
-
Install the Application
mcp install src/universal_mcp_google_drive/server.py
📁 Project Structure
.
├── src/
│ └── universal_mcp_google_drive/
│ ├── __init__.py # Package initializer
│ ├── server.py # Server entry point
│ ├── app.py # Application tools
│ └── README.md # List of application tools
├── tests/ # Test suite
├── .env # Environment variables for local development
├── pyproject.toml # Project configuration
└── README.md # This file
📄 License
This project is licensed under the MIT License.
Generated with MCP CLI — Happy coding! 🚀
Metadata
Release files for universal-mcp-google-drive 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| universal_mcp_google_drive-0.1.5.tar.gz | 164.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| universal_mcp_google_drive-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 188.9 kB
Release files / universal_mcp_google_drive-0.1.5.tar.gz
| Download URL | universal_mcp_google_drive-0.1.5.tar.gz |
|---|---|
| Size | 164.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0fab29fc22a9c50a96fc7eddcc23cd8f777d10828f6ecd919cd84c2cf6b5a4c8
|
|
BLAKE2b-256 checksum How to use checksums |
ab80eddd03bceaa3cb1cd18c2c333eb3f449672b43f9387ee93e4eb90bb4b8cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Release files / universal_mcp_google_drive-0.1.5-py3-none-any.whl
| Download URL | universal_mcp_google_drive-0.1.5-py3-none-any.whl |
|---|---|
| Size | 24.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a372fad84fba6145457d9ab923b07413294403c50677eaf0809c87bf9c2eb39a
|
|
BLAKE2b-256 checksum How to use checksums |
65d46e9e98bf21f462ab9a0ac977ea092c3a89a6d33bba3d79116ca07316e1d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Security for universal-mcp-google-drive 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.