MCP server
Google Drive
Let an AI client search, read, and create Drive files only after the account and folder scope are reduced.
Published by the company that makes the product.
What it can access
OAuth grants the connector the connected user's permitted Drive capabilities. The effective scope can include every file that account can access.
Security note
Google labels Workspace MCP servers Developer Preview. Use a dedicated workshop account or narrowly shared folder, not an account that can see case files.
Do you need it?
Connect only if repeated copy and paste from a controlled Drive folder is the real bottleneck. For one or two files, upload public copies manually instead.
Capability and permissions
The official hosted server uses Google OAuth and inherits the connected user’s permitted Drive capabilities. This can expose every file that account can access, not just the file named in a prompt.
Least-privilege setup
As of 2026-09-01, Google labels Workspace MCP servers Developer Preview. Use the current Google setup guide and a compatible client. Create a workshop Google account, share one disposable folder with it, connect through Google’s OAuth screen, and reject permissions you cannot explain.
Harmless success test
Put one text file named mcp-test.txt in the folder. Ask the client to find and summarise it. Confirm it cannot find a file outside that folder or account.
Disable, revoke, remove
Disconnect the server in the AI client, then remove the client’s access from the Google Account third-party connections page. Remove the workshop account from the folder and delete test files.
When not to connect
Do not connect an account that can see case files, personnel records, legal correspondence, source identities, or an organisation-wide shared drive.