Google Drive (Official)
Connect AI assistants to Google Drive using Google's official remote MCP server with an admin-supplied OAuth client.
Last updated
Connect AI assistants to Google Drive using Google's official remote MCP server with an admin-supplied OAuth client.
Early Access — Reach out to your Natoma representative for access.
Type: Official
Source Type: Remote URL
Source: https://drivemcp.googleapis.com/mcp/v1
Description: Google Drive MCP server is Google's official remote MCP integration for Drive. It enables searching, reading, creating, and managing files and permissions through OAuth.
In the Google Cloud Console, select the project that should own the OAuth client.
Navigate to APIs & Services > Library, search for Google Drive API, and click Enable.
Navigate to Google Auth Platform > Branding and configure the OAuth Consent Screen (App name, support email, audience, contact email).
Under Data Access > Add or Remove Scopes, add (one per line):
drive.readonly
drive.fileNavigate to Google Auth Platform > Clients > Create Client and select Web application.
Under Authorized redirect URIs, click + Add URI and enter:
Use exactly this redirect URI — Google will reject the OAuth flow if it doesn't match.
Click Create and copy the Client ID and Client Secret.
In Natoma, an admin adds Google Drive under Apps and enters the Client ID and Client Secret.
When prompted while creating the connection in Natoma, click Authorize.
Last updated
https://api.natoma.app/mcp/server/callback