Google Drive MCP server: connect AI agents to Google Drive from the EU

Google Drive is Google's file storage and sharing service, used with Docs, Sheets and Slides across Google Workspace. Google LLC is based in Mountain View, California.

Google publishes official remote MCP servers for several Workspace products. The Drive server runs at https://drivemcp.googleapis.com/mcp/v1 and is in Developer Preview, so tools and behaviour may still change. It acts with the OAuth access of the signed-in user and sees only files that user can open. It offers searching, reading, metadata, permissions, creating and copying, but no tools for deleting files or changing sharing.

A sales agent can find the latest proposal for a customer, read it and answer questions about agreed terms with a link to the file. A finance agent can copy a monthly report template and fill a new file with figures gathered from other connectors.

Legal and operations teams can ask "which contracts in this folder are shared outside the company?" and get an answer from file permissions. Project agents can read the documents linked in a brief before drafting a plan.

Google's Workspace MCP servers need a Google Cloud project with the Drive API and the Drive MCP service enabled, and an OAuth client configured for that project. Your Workspace admin may need to allow the app.

Add the Google Drive connector on inference.eu, enter your OAuth client details and sign in with the Google account the agent should use. Choose the narrowest scopes that work. Tokens are stored encrypted in the EU and used only by the agents you allow; the user can revoke access in their Google account settings.

Files are fetched from Google's own MCP endpoint, so data stays with Google, a US company, as it does for your other Drive integrations. Google Workspace offers data regions for files on some editions, which control where content is stored at rest.

On inference.eu, the model that reads your files runs in EU data centres, and your Google credentials are stored encrypted in the EU. Drive often holds contracts, HR files and customer data, so connect agents through an account that only has access to the folders they need.

Most Drive tools only read, which limits the risk to what the agent can see. Creating and copying files adds content to Drive and can place it in shared folders that other people see.

On inference.eu you can let searches and reads run on their own and require a person's approval before an agent creates or copies a file. Because the server reads permissions as well as content, keep in mind that an agent can report who has access to a document; treat that as sensitive information in its answers.