Connect Google Drive to Andromity with the Google Drive MCP server

Google hosts an official Google Drive MCP server at https://drivemcp.googleapis.com/mcp/v1. With it, Andromity can search your Drive, read specs and notes stored there, and create or copy files while it works on your code.

The server is part of the Google Workspace MCP servers, which Google labels Developer Preview. Sign-in uses your own Google Cloud OAuth client, so setup takes a few extra steps in Google Cloud before you connect.

What the agent can do with Google Drive

• Search files (search_files) and list recent files (list_recent_files).
• Read file content (read_file_content) and download it (download_file_content).
• Get file metadata (get_file_metadata).
• Check a file's sharing permissions (get_file_permissions).
• Create files (create_file) and copy files (copy_file).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Google Drive MCP server”.

• Search my Drive for the payments API design doc and summarize the retry requirements.
• Read the spec file named 'Export format v2' in Drive and implement the CSV writer to match it.
• Check the sharing permissions on the architecture doc in Drive and tell me who has access.
• List my recently opened Drive files and tell me which ones relate to the auth module in this repo.

Connect Google Drive

1. Join the Google Workspace Developer Preview Program, which Google requires for its Workspace MCP servers.
2. In a Google Cloud project, enable the Google Drive API and the Google Drive MCP API (drivemcp.googleapis.com).
3. Configure the OAuth consent screen. For an External user type, add yourself as a test user, and add the Drive scopes you need under Data Access.
4. Create an OAuth client of type Web application, select 'Use this client for an AI-powered agent', and add the redirect URI http://127.0.0.1:54321/callback.
5. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Google Drive and select Connect.
6. Enter the client ID and secret, then sign in with Google in your browser. Andromity requests offline access so sign-in refreshes.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• The agent acts with the permissions of the Google account you sign in with.
• Google warns about indirect prompt injection: use only trusted tools, be careful with content from unverified sources, and review actions the agent takes on your behalf.
• Andromity's permission modes apply to every Drive tool call. In TRUST mode, tools such as create_file ask first.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Developer Preview: Google may change the server, and Workspace Developer Preview membership is required.
• Google states that from November 11, 2026, Workspace MCP servers will reject OAuth clients that are not marked 'Use this client for an AI-powered agent'.

Questions

Does Google Drive have an official MCP server?

Yes. Google hosts one at https://drivemcp.googleapis.com/mcp/v1 as part of its Workspace MCP servers, currently in Developer Preview.

Do I need my own OAuth client to connect Google Drive to Andromity?

Yes. Google's Workspace MCP servers use OAuth 2.0 with a client you create in Google Cloud. Andromity asks for the client ID and secret when you connect.

Why does Google ask me to sign in every hour?

Google says this happens when the client does not get a refresh token, and recommends adding access_type=offline to the authorization request. Andromity requests offline access.

Sources

This guide is based on Google Drive’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• MCP Reference: drivemcp.googleapis.com
• Configure the Google Workspace MCP servers

Google Drive is a trademark of its owner. Andromity is not affiliated with or endorsed by Google Drive.