Google Drive MCP Integration

Weldable's Google Drive MCP integration gives your AI agents direct access to your files, folders, and sharing settings. Search across your entire Drive, organize documents into folders, manage permissions, and track changes, all through natural language. Connect once via OAuth and your agent gets 20 Google Drive actions immediately.

Google now offers official MCP support across its services, and the protocol is becoming the standard for how AI agents interact with tools. Weldable takes this further by combining Drive with other integrations like Slack, Gmail, and Google Sheets in automated workflows.

Use cases

Document retrieval for research

Your agent searches Drive for all documents matching a topic, pulls metadata like last modified date and owner, then summarizes what it found. Ask "find all Q1 budget spreadsheets" and it queries Drive using MIME type filters and name matching, returning exactly the files you need without scrolling through folders.

Project folder scaffolding

When a new project kicks off, your agent creates a standard folder structure: separate folders for briefs, deliverables, and reviews. It can copy template documents into the right locations and share the top-level folder with the project team. A task that takes 10 minutes by hand finishes in seconds.

Sharing audit and cleanup

Your agent lists permissions on sensitive files and flags anything shared with "anyone" or external domains. It can downgrade public files to organization-only access, remove ex-employees who still have edit rights, and post a summary of changes to Slack. Useful for quarterly access reviews.

Cross-tool document workflows

Pair Drive with other Weldable integrations for multi-step automation. Your agent can read a Google Sheet of weekly metrics, create a summary document in Drive, share it with stakeholders, and post a link to the relevant Slack channel. Or watch for new files in a specific folder and notify a Discord channel when something lands.

Change monitoring

Your agent checks what changed in Drive since the last review using the changes API. It filters for modified spreadsheets or new documents in a shared drive, then compiles a digest. Run this on a schedule to keep your team aware of document activity without anyone manually checking.

How it works

Connect your Google account through a one-click OAuth flow. Weldable requests Drive permissions to search, read metadata, create files, manage sharing, and track changes. Tokens refresh automatically.

Once connected, talk to your agent in plain English. Say "find the slide deck from last month's board meeting" and Weldable translates that into a Drive API search query, resolves the right MIME type for presentations, and returns matching files with their links. Your agent can chain multiple actions: search for a file, check who has access, add a new collaborator, and post the sharing link to Slack.

File operations work the same way. "Create a folder called Q2 Planning in the Marketing shared drive" handles the shared drive lookup, folder creation with the correct MIME type, and returns a confirmation with the folder link.

Tips

Drive search queries are powerful but specific. The q parameter supports operators like name contains 'budget', modifiedTime > '2025-01-01', and mimeType = 'application/vnd.google-apps.spreadsheet'. You can combine these with and/or. When your agent searches, give it specific terms and it will construct the right query.

Know your Google MIME types. Google Docs, Sheets, Slides, and folders each have their own MIME types (application/vnd.google-apps.document, application/vnd.google-apps.spreadsheet, application/vnd.google-apps.presentation, application/vnd.google-apps.folder). These are different from standard file MIME types. When creating files, the MIME type determines whether you get a native Google file or an uploaded binary.

Moving files requires both addParents and removeParents. To move a file to a new folder, you set addParents to the destination folder ID and removeParents to the current folder ID. Just setting addParents creates a shortcut-like multi-parent situation, which is usually not what you want.

Use fields to control response size. Every Drive action accepts a fields parameter. Instead of getting the full file metadata object, request only what you need: fields: "files(id,name,webViewLink)". This keeps responses lean and helps your agent process results faster.

Shared drives need the supportsAllDrives flag. Files in shared drives (formerly Team Drives) are invisible unless you set supportsAllDrives: true and includeItemsFromAllDrives: true. If your agent can not find a file you know exists, this is usually why.

Avoid sorting by createdTime on large collections. The Drive API is optimized for modifiedTime sorting but can return incomplete results when sorting by createdTime across large file sets. Prefer orderBy: "modifiedTime desc" for reliable results.