How to set up the Google Drive MCP server

Google Drive MCP provides access to files and metadata that the authorized Workspace user can access. It uses Google OAuth 2.0 only, after the Workspace Developer Preview and required Google APIs are enabled.

This guide covers the Google-side preparation for the Google Drive remote MCP server. It applies to any compatible MCP client. The Google Drive agent template is separate from this Cloud-project and OAuth setup.

Google Drive MCP is part of the Google Workspace Developer Preview Program. Its Streamable HTTP endpoint is https://drivemcp.googleapis.com/mcp/v1 and it uses OAuth 2.0.

Choose a connection method

Google Workspace MCP supports Google OAuth 2.0 for Drive; it does not offer a bearer-token alternative for this server. The Google Workspace MCP configuration guide is the source of truth for the endpoint, enabled APIs, OAuth client requirements, and supported scopes.

Recommended: Google OAuth for Workspace MCP

Complete the following vendor-side setup before connecting the MCP server.

• Join the Google Workspace Developer Preview Program.
• Create a dedicated Google Cloud project, separate from unrelated production integrations.
• Prepare a test Drive identity with a small, known folder tree; do not start with a broad production Drive account.
• Select this project, then click Enable on both services: Google Drive API (drive.googleapis.com) and Google Drive MCP API (drivemcp.googleapis.com).
• In Google Auth Platform, complete Branding and Audience.
• Use an Internal app for a single Workspace organization. For an External app in testing, add the smoke-test identity as a test user.

Create a read-only OAuth client

Under Google Auth Platform → Data Access, add only:

https://www.googleapis.com/auth/drive.readonly

Then create a Web application OAuth client in Clients using Google Auth Platform → Clients → Create client. Register this exact redirect URI:

https://api.domesystems.ai/oauth/callback

Select Use this client for an AI-powered agent before creating it. Store the client ID and secret securely. Do not add drive.file or another write-capable scope unless a separately reviewed server needs to create or modify files.

Request access_type=offline when the MCP client supports custom authorization parameters. This lets Google issue the refresh token needed to avoid frequent reauthorization; offline_access alone does not do so.

Verify Drive MCP

Use this checklist to confirm the MCP server is connected with the intended access.

• Connect to https://drivemcp.googleapis.com/mcp/v1 with the client ID and secret.
• Authorize the dedicated test Drive identity.
• Confirm that Drive MCP tools appear.
• Search for and retrieve metadata from a known test file.
• Confirm that copying, uploading, sharing, moving, and editing are unavailable.

If consent completes but the server exposes no Drive tools, check that both APIs were enabled in the project that owns the OAuth client. If Google rejects the connection, re-check the client type, AI-agent setting, exact redirect URI, test-user access, and requested scope.

Google's Workspace MCP configuration guide is the authority for the current endpoint, APIs, OAuth contract, and scopes.

Troubleshooting

If the setup does not work as expected, check these common causes.

• If Google rejects authorization, re-check the Developer Preview enrollment, client type, AI-agent setting, exact redirect URI, test-user access, and requested scope.
• If authorization succeeds but Drive MCP tools do not appear, confirm that both the Google Drive API and Google Drive MCP API are enabled in the Cloud project that owns the OAuth client.
• If a known file is unavailable, verify the test identity's file sharing and drive.readonly grant before widening access.

Next steps

Deploy the Google Drive agent template to create a governed agent in Dome that can work with the authorized Drive files, with the template's included model, tools, and rules.