Google Drive to MCP: Drive Google Drive from any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Google Drive, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Google Drive

Let your AI work in Google Drive: search files and folders in My Drive and shared drives, read Google Docs, Sheets and Slides as text, see details, comments and who has access, create folders and text files (or new Docs and Sheets from text), copy, rename, move, share and trash. Personal Google accounts and Google Workspace.

Setup

1. Open console.cloud.google.com, pick or create a project, then go to APIs & Services → Library and enable the Google Drive API.
2. Open APIs & Services → OAuth consent screen. Choose Internal if you are on Google Workspace (the simplest option), otherwise External. For External, set the publishing status to In production: while the app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own account you can click through the "unverified app" warning.
3. Open APIs & Services → Credentials → Create credentials → OAuth client ID, choose the application type Web application and add the authorized redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback. If you host AnythingMCP yourself, enter https://your-anythingmcp-host/api/mcp-oauth/callback instead.
4. Paste the client ID into GOOGLE_CLIENT_ID and the client secret into GOOGLE_CLIENT_SECRET, then install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account whose Drive the AI should use. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector: Gmail, Google Calendar, Google Drive, Google Sheets, Google Docs, Google Tasks, Search Console, Analytics and Ads. Enable each API in that project, reuse the same client ID and secret, and authorize each connector once. Each one asks only for its own permissions.

Google verification: Google classifies full Drive access as a restricted permission. An Internal app, used only by accounts of the Workspace organization that owns the Cloud project, needs no verification. An External app that other people use shows a "Google hasn't verified this app" warning and is capped at 100 users until it passes Google's verification, which for restricted permissions includes a security assessment. For your own account, an External app In production works after you continue past the warning.

Reading files: Google Docs, Sheets and Slides are read as text (for a Sheet, its first tab; the Google Sheets connector reads any range). Uploaded files such as PDFs, Word documents or images cannot be read or downloaded through this connector: the AI gives you their link instead.

Permissions: the connector asks for https://www.googleapis.com/auth/drive, because searching and reading files it did not create itself needs full Drive access. Narrower permissions such as drive.file only see files the app created.

Read-only setup: change the scope in the connector's OAuth settings to https://www.googleapis.com/auth/drive.readonly, authorize again and disable gdrive_create_folder, gdrive_create_text_file, gdrive_copy_file, gdrive_update_file, gdrive_share_file and gdrive_trash_file.

Switched off at install: gdrive_share_file and gdrive_trash_file. Sharing is off on purpose: it gives other people access to your files, and a document the AI reads could contain text asking it to share something. Turn a tool on only if the AI really needs it. Trashed items stay restorable from Drive's trash for 30 days, and nothing in this connector deletes files permanently.

Common errors: 401 means the authorization expired or was revoked (always after 7 days while the consent screen is in Testing): click Authorize with Provider again. 403 accessNotConfigured means the Google Drive API is not enabled in the Cloud project. 403 insufficientPermissions means the scope does not allow the call (a write on a read-only setup); 403 insufficientFilePermissions means your account may not change that file. 404 notFound means the id is wrong or the file is not visible to this account.

The connector does not upload or download binary files, never deletes permanently, cannot remove anyone's access and does not handle revisions, labels or Drive activity.

Prerequisites: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick Google Drive and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "Find the documents about the Acme project changed in the last two weeks and summarize what's in them."
• "Who has access to the folder Contracts 2026?"
• "Create a folder Q4 Reports and save this summary in it as a Google Doc."
• "Read the comments on the proposal draft and list the questions that are still open."

Next steps

• Connect to Claude
• Connect to ChatGPT