Upload, share and delete are all here, not just read-only browsing, and get_file_content pulls a text file into the conversation without it ever touching your disk. Access runs through a MewCP account that holds the Google connection, so the setup happens in their dashboard instead of a local config file.
A Google Drive server hosted on the MewCP platform. It covers the whole file lifecycle rather than browsing alone — list and search, read metadata or text content, upload and download, create folders, share, delete — and takes Drive's own query language, so filters you already write carry over unchanged.
- Files listed by folder, or found with Drive query expressions on name, type, modified date or full text
- Full metadata for one file or folder, owners included
- The decoded text of a file returned straight into the conversation, with nothing written to disk
- Uploads and downloads between Drive and a local path, with destination folder and MIME type your choice
- Folders created, nested inside a parent when you name one
- Sharing granted to one person by email or to anyone with the link, at reader, commenter or writer level
- Deletion of a file or folder, which the tool performs permanently rather than moving it to trash
Two things travel with every call: an API key for your MewCP account, and an identifier for the Google credential held there. You never hand Google credentials to the server directly — the Google account is connected through the MewCP dashboard over OAuth first. Calls draw on that account's credit balance, so heavy use is limited by the plan rather than by Drive.