How to integrate Google Drive MCP with Grok Build

Connect Grok Build to Google Drive MCP. Create a new folder named 'invoices', share last uploaded file with your team, and more from your terminal, with authentication handled for you.

Google Drive logoGoogle Drive
Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

76 Tools7 Triggers

How to integrate Google Drive MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Google Drive account to Grok Build through Composio, so it can create a new folder named 'Invoices', share last uploaded file with your team, add comment to project proposal document, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Google Drive with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Google Drive integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Google Drive account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Google Drive to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Google Drive account through Composio. On the first Google Drive action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Google Drive

  • Create a new folder named 'Invoices'
  • Share last uploaded file with your team
  • Add comment to project proposal document
  • Copy template file to today's reports folder

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Google Drive scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Google Drive action and event your agent gets out of the box.

Insert File Parent (v2)

Tool to add a parent folder for a file using Google Drive API v2.

Insert Property (v2 API)

Tool to add a property to a file, or update it if it already exists (v2 API).

Copy file with advanced options

Creates a copy of a file and applies any requested updates with patch semantics.

Create Comment

Tool to create a comment on a file in Google Drive.

Create Shared Drive

Tool to create a new shared drive.

Create File or Folder

Creates a new file or folder in Google Drive.

Create a File from Text

Creates a new file in Google Drive from provided text content (up to 10MB), supporting various formats including automatic conversion to Google Workspace types.

Create a folder

Creates a new folder in Google Drive, optionally within an EXISTING parent folder specified by its ID or name.

Create Permission

Tool to create a permission for a file or shared drive.

Create Reply

Tool to create a reply to a comment in Google Drive.

Create Shortcut to File/Folder

Tool to create a shortcut to a file or folder in Google Drive.

Delete Child (v2)

Tool to remove a child from a folder using Google Drive API v2.

Delete Comment

Permanently deletes a comment thread (and all its replies) from a Google Drive file — this action is irreversible.

Delete Shared Drive

Tool to permanently delete a shared drive.

Delete Parent (v2)

Tool to remove a parent from a file using Google Drive API v2.

Delete Permission

Deletes a permission from a file by permission ID.

Delete Property (v2 API)

Tool to delete a property from a file using Google Drive API v2.

Delete Reply

Tool to delete a specific reply by reply ID.

Delete Revision

Tool to permanently delete a file revision.

Download a file from Google Drive

Downloads a file from Google Drive by its ID.

Download file via operation

Tool to download file content using long-running operations.

Edit File

Updates an existing Google Drive file with binary content by overwriting its entire content with new text (max 10MB).

Empty Trash

Tool to permanently and irreversibly delete ALL trashed files in the user's Google Drive or a specified shared drive.

Export Google Workspace file

Exports a Google Workspace document to the requested MIME type and returns exported file content.

Find file

The comprehensive Google Drive search tool that handles all file and folder discovery needs.

Find folder

Tool to find a folder in Google Drive by its name and optionally a parent folder.

Generate File IDs

Generates a set of file IDs which can be provided in create or copy requests.

Get about

Tool to retrieve information about the user, the user's Drive, and system capabilities.

Get App

Tool to get information about a specific Drive app by ID.

Get Changes Start Page Token

Tool to get the starting pageToken for listing future changes in Google Drive.

Get Child Reference (v2)

Tool to get a specific child reference for a folder using Drive API v2.

Get Comment

Tool to get a comment by ID.

Get Shared Drive

Tool to get a shared drive by ID.

Get File Metadata

Tool to get a file's metadata by ID.

Get Property (v2)

Tool to get a property by its key using Google Drive API v2.

Get Parent Reference (v2)

Tool to get a specific parent reference for a file using Drive API v2.

Get Permission

Gets a permission by ID.

Get Permission ID for Email

Tool to get the permission ID for an email address using the Drive API v2.

Get Reply

Tool to get a specific reply to a comment on a file.

Get Revision

Tool to get a specific revision's metadata (name, modifiedTime, keepForever, etc.

Delete folder or file

Tool to delete a file or folder in Google Drive.

Hide Shared Drive

Tool to hide a shared drive from the default view.

Insert Child Into Folder (v2)

Tool to insert a file into a folder using Drive API v2.

List Access Proposals

Tool to list pending access proposals on a file.

List Approvals

Tool to list approvals on a file for workflow-based access control.

List Changes

Tool to list the changes for a user or shared drive.

List Folder Children (v2)

Tool to list a folder's children using Google Drive API v2.

List Comments

Tool to list all comments for a file in Google Drive.

List File Labels

Tool to list the labels already applied to a file in Google Drive.

List Properties (v2 API)

Tool to list a file's properties in Google Drive API v2.

List Permissions

Tool to list a file's permissions.

List Replies to Comment

Tool to list replies to a comment in Google Drive.

List File Revisions

Tool to list a file's revision metadata (not content) in Google Drive.

List Shared Drives

Tool to list the user's shared drives.

Modify File Labels

Modifies the set of labels applied to a file.

Move File

Tool to move a file from one folder to another in Google Drive.

Patch Permission

Tool to update a permission using patch semantics.

Patch Property (v2 API)

Tool to update a property on a file using PATCH semantics (v2 API).

Resumable Upload

Tool to start and complete a Google Drive resumable upload session.

Stop Watch Channel

Tool to stop watching resources through a specified channel.

Trash File

Tool to move a file or folder to trash (soft delete).

Unhide Shared Drive

Tool to unhide a shared drive.

Untrash File

Tool to restore a file from the trash.

Update Comment

Tool to update an existing comment on a Google Drive file.

Update Shared Drive

Tool to update the metadata for a shared drive.

Update File Metadata (PATCH v2)

Tool to update file metadata using the Drive API v2 PATCH method.

Update Property (v2 API)

Tool to update a property on a file using Google Drive API v2.

Update File (Metadata)

Updates file metadata.

Update File Revision Metadata

Updates ONLY the metadata properties of a specific file revision (keepForever, published, publishAuto, publishedOutsideDomain).

Update Permission

Tool to update a permission with patch semantics.

Update Reply

Tool to update a reply to a comment on a Google Drive file.

Upload File

Uploads a file (max 5MB) to Google Drive, placing it in the specified folder or root if no valid folder ID is provided.

Upload File from URL to Drive

Tool to fetch a file from a provided URL server-side and upload it into Google Drive.

Upload/Update File Content

Tool to update file content in Google Drive by uploading new binary content.

Watch Drive Changes

Tool to subscribe to changes for a user or shared drive in Google Drive.

Watch File for Changes

Tool to subscribe to push notifications for changes to a specific file.

FAQ

Frequently asked questions

A standalone Google Drive MCP server gives Grok Build a fixed set of Google Drive tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Google Drive and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Google Drive data and credentials are handled to that standard.

Start with Google Drive.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Drive tool your agent needs.Free to start.

Start building