Ctrlk
Log inSign up

Google Drive (Natoma)

Connect AI assistants to Google Drive using Natoma's hosted OAuth MCP server.

Early Access — This server is currently in early access. Features and configuration may change.

Type: Natoma Hosted

Source Type: Remote URL

Description: Google Drive MCP server provides AI assistants with access to Google Drive. This is a subset of the available tools in the Google Workspace MCP Server, created by Natoma.

Setup

Step 1: Enable the Google Drive API

  1. Go to the Google Cloud Console.

  2. Make sure your target project is selected in the top project dropdown.

  3. In the left sidebar, navigate to APIs & Services > Library.

  4. Search for Google Drive API and click on it.

  5. Click Enable.

You can also enable it directly: Google Drive API

Step 2: Configure the OAuth Consent Screen

  1. In the Google Cloud Console, go to Google Auth Platform > Branding (or search "OAuth consent screen" in the top search bar).

  2. If the Auth Platform isn't set up yet, click Get Started and fill in the following:

    • App name: Drive MCP Server

    • User support email: your email address — click Next

    • Audience: Select Internal — click Next

    • Contact email: your email address

  3. Agree to the Google API Services User Data Policy, then click Continue > Create.

  4. Click Data Access in the left menu, then click Add or Remove Scopes.

  5. In the panel that appears, scroll down to Manually add scopes and paste in both scopes (one per line):

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

  6. Click Add to Table, then Update, then Save.

Step 3: Create an OAuth 2.0 Client ID

  1. Go to Google Auth Platform > Clients > Create Client.

  2. Select Web application as the application type.

  3. Name the application.

  4. In the Authorized redirect URIs section, click + Add URL and enter:

Use exactly this redirect URI — Natoma will not complete the OAuth flow if it doesn't match.

  1. Click Create and copy the Client ID and Client Secret.

Step 4: Configure the Connector in Natoma

  1. Log in to your Natoma workspace as an Admin and navigate to Apps, then search for Google Drive (Natoma).

  2. Click + > Allow Personal Connections.

  3. In the connector configuration dialog, enter the following:

Field
Value

Server name

Google Drive MCP (or any descriptive label)

OAuth Client ID

The Client ID from Step 3

OAuth Client Secret

The Client Secret from Step 3

  1. Save the connector. Natoma will initiate an OAuth consent flow to authorize access to your Google Drive.

  2. Click Test Connections to see the available tools that are connected to Natoma.

drive.readonly grants read access to all files the user can see. drive.file is more restrictive — it limits access to files created or explicitly opened by the app. For most Natoma workflows, both scopes are recommended: drive.readonly enables broad search and read operations, while drive.file enables file creation. The broader drive scope (full access) satisfies all requirements but is not recommended under least-privilege best practices.

Last updated