MewCP Google Drive MCP

What it is

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.

What you get

• 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

Requirements

Every call carries one thing: the API key for your MewCP account, sent as a Bearer header. 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.

Setup effort

Add the hosted endpoint plus a key — paste it into your client, then supply credentials

Tools you get

9 tools named in the project's documentation.

Requires

• A MewCP account and its API key (MEWCP_KEY, dashboard → Developer) — the Hobby tier is free (unlimited servers, 20K actions/month)
• The Google Drive server enabled in your MewCP toolset — the gateway only reaches servers you have enabled
• Your Google account connected under Credentials in the MewCP dashboard (OAuth)

Where it runs

All 3 documented clients connect to a hosted endpoint.